@strapi/pack-up
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prettier-plugin-packagejson | AI (phantom-deps): Used via config file, not direct import; expected for prettier plugins. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 21 / 20 | |
| 5.1.0 | 21 / 20 | |
| 5.0.2 | 21 / 20 | |
| 5.0.1 | 21 / 20 |
v5.1.0
2 findingsThis version was published by a different npm account (jhoward1994) than the most recent previously approved version (alexandrebodin) on 2025-02-11. It has since remained available on npm for 522 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.