@nice-move/prettier-plugin-package-json
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD publisher switch with SLSA attestation is a provenance improvement, not compromise. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Consistent with automated CI release pipeline. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Bundled build output growth from CI packaging, no malicious content shown. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.9.5 | 0 / 14 | |
| 0.9.4 | 0 / 14 | |
| 0.9.2 | 0 / 14 | |
| 0.9.1 | 0 / 14 | |
| 0.9.0 | 0 / 14 |
v0.9.5
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. 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.
v0.9.4
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. 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.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.