init-package-json
A node module to get your node module started
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @npmcli/package-json is an official npm CLI package replacing read-package-json. Legitimate dependency change. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate npm CLI team transition from original individual maintainers to the GitHub/npm org team. Well-documented, stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance; this is the npm CLI team's standard release pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all known npm CLI team members (gar, npm-cli-ops, etc.). Stable for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original maintainers (isaacs, zkat, etc.) left the npm CLI team years ago; removal is expected and stable. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has been actively published; dormancy is only relative to last vetted version (v1.9.1). Not a real signal. | ai | |
| dependencies | unvetted-dep:validate-npm-package-license | AI (dependencies): validate-npm-package-license is a well-known, legitimate npm utility for SPDX license validation; its use here is expected and stable across versions. | ai | |
| dependencies | unvetted-dep:npm-package-arg | AI (dependencies): npm-package-arg is a core npm CLI utility maintained by the npm/GitHub org; no security concern. | ai | |
| dependencies | unvetted-dep:@npmcli/package-json | AI (dependencies): @npmcli/package-json is an official npm org scoped package; stable and widely used in the npm CLI ecosystem. | ai | |
| dependencies | unvetted-dep:validate-npm-package-name | AI (dependencies): validate-npm-package-name is a canonical npm org utility; no security concern. | ai | |
| dependencies | unvetted-dep:promzard | AI (dependencies): promzard is an official npm org package (github.com/npm/promzard), a stable dependency of init-package-json across many versions. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 9.0.0 | 6 / 4 | |
| 8.2.5 | 6 / 4 | |
| 8.2.4 | 7 / 4 | |
| 8.2.3 | 7 / 4 | |
| 8.2.2 | 7 / 4 | |
| 8.2.1 | 7 / 4 | |
| 8.2.0 | 7 / 4 | |
| 8.1.1 | 7 / 4 | |
| 8.1.0 | 7 / 4 | |
| 8.0.0 | 7 / 4 | |
| 7.0.2 | 7 / 4 | |
| 7.0.1 | 7 / 4 | |
| 7.0.0 | 7 / 4 | |
| 6.0.3 | 7 / 4 | |
| 1.9.1 | 8 / 3 |
v9.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.4
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-11-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.3
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-11-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.2
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (fritzy, gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.1
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (fritzy, gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (fritzy, gar, saquibkhan, npm-cli-ops, reggi, hashtagchris, owlstronaut). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
3 findingsAll previous maintainers (isaacs, othiym23, iarna, zkat) were replaced by new maintainers (fritzy, gar, saquibkhan, npm-cli-ops, reggi, hashtagchris). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2024-12-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-26. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.