@commercelayer/cli-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@commercelayer/js-auth | AI (dependencies): First-party @commercelayer org dependency; stable pattern across all versions of this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 5.11.2 | 5 / 15 | |
| 5.11.1 | 5 / 15 | |
| 5.11.0 | 5 / 15 | |
| 5.10.8 | 5 / 17 | |
| 5.10.7 | 5 / 17 | |
| 5.10.6 | 5 / 17 | |
| 5.10.5 | 5 / 17 | |
| 5.10.4 | 5 / 17 | |
| 5.10.3 | 5 / 17 | |
| 5.10.2 | 5 / 17 | |
| 5.10.1 | 5 / 17 | |
| 5.10.0 | 5 / 17 | |
| 5.9.0 | 5 / 17 | |
| 5.8.1 | 5 / 17 | |
| 5.8.0 | 5 / 17 | |
| 5.7.2 | 5 / 17 | |
| 5.7.1 | 5 / 17 | |
| 5.7.0 | 5 / 17 | |
| 5.6.4 | 5 / 17 | |
| 5.6.3 | 5 / 17 | |
| 5.6.2 | 5 / 17 | |
| 5.6.1 | 5 / 17 | |
| 5.6.0 | 5 / 17 | |
| 5.5.0 | 5 / 17 | |
| 5.4.3 | 5 / 17 | |
| 5.4.2 | 5 / 17 | |
| 5.4.1 | 5 / 17 | |
| 5.4.0 | 5 / 17 | |
| 5.3.1 | 5 / 17 | |
| 5.3.0 | 5 / 17 | |
| 5.2.4 | 5 / 17 | |
| 5.2.3 | 5 / 17 | |
| 5.2.2 | 5 / 18 | |
| 5.2.1 | 5 / 18 | |
| 5.2.0 | 5 / 18 | |
| 5.1.1 | 5 / 18 | |
| 5.1.0 | 5 / 18 | |
| 5.0.5 | 5 / 18 | |
| 5.0.4 | 5 / 18 | |
| 5.0.3 | 5 / 18 | |
| 5.0.2 | 5 / 18 |
v5.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.