@commercelayer/cli-plugin-cleanups
Commerce Layer CLI Cleanups plugin
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): Transition to GitHub Actions publishing is confirmed by SLSA provenance attestation; stable for this org's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate publish pipeline. | ai | |
| provenance | slsa-provenance | AI (provenance): Org uses GitHub Actions for CI/CD releases; SLSA provenance is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:node-notifier | AI (phantom-deps): node-notifier is a declared runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.2.5 | 9 / 18 | |
| 3.2.4 | 9 / 18 | |
| 3.2.3 | 9 / 18 | |
| 3.2.2 | 9 / 18 | |
| 3.2.1 | 9 / 18 | |
| 3.2.0 | 9 / 19 | |
| 3.1.13 | 9 / 19 | |
| 3.1.12 | 9 / 19 | |
| 3.1.11 | 9 / 19 | |
| 3.1.10 | 9 / 19 | |
| 3.1.9 | 9 / 19 | |
| 3.1.8 | 9 / 19 | |
| 3.1.7 | 9 / 19 | |
| 3.1.6 | 9 / 19 | |
| 3.1.5 | 9 / 19 | |
| 3.1.4 | 9 / 19 | |
| 3.1.3 | 9 / 19 | |
| 3.1.2 | 9 / 19 | |
| 3.1.1 | 9 / 19 | |
| 3.1.0 | 9 / 19 | |
| 3.0.1 | 8 / 19 | |
| 3.0.0 | 8 / 19 |
v3.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.