normalize-package-data 0.1.1

Normalizes data that can be found in package.json files.

normalize-package-data@0.1.1 was published on 2013-04-23. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All normalize-package-data versions · Permanent reference to 0.1.1 · Latest release

Package specifications

Version0.1.1
License declarationNot declared
Published2013-04-23T19:27:10.842Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/normalize.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars204
Repository forks54

Install normalize-package-data 0.1.1

npm install normalize-package-data@0.1.1
pnpm add normalize-package-data@0.1.1
yarn add normalize-package-data@0.1.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
SAST8/10 — SAST tool detected but not run on all commits

Evidence and freshness