@pob/pretty-pkg
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 14.0.0 | 1 / 0 | |
| 13.2.3 | 1 / 0 | |
| 13.2.2 | 1 / 0 | |
| 13.2.1 | 1 / 0 | |
| 13.2.0 | 1 / 0 |
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.