stringify-package 1.0.0

stringifies npm-written json files

stringify-package@1.0.0 was published on 2018-07-18. Its manifest declares 0 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.

Deprecated: This module is not used anymore, and has been replaced by @npmcli/package-json

All stringify-package versions · Permanent reference to 1.0.0 · Latest release

Package specifications

Version1.0.0
License declarationISC
Published2018-07-18T18:31:40.703Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.57 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars10
Repository forks7

Install stringify-package 1.0.0

npm install stringify-package@1.0.0
pnpm add stringify-package@1.0.0
yarn add stringify-package@1.0.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    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-Review1/10 — Found 1/9 approved changesets -- score normalized to 1
    Maintained0/10 — project is archived
    Binary-Artifacts10/10 — no binaries found in the repo
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
    Security-Policy0/10 — security policy file not detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches

    Evidence and freshness