@commercelayer/cli-plugin-exports
Commerce Layer CLI Exports 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@commercelayer/sdk | AI (dependencies): First-party Commerce Layer SDK; expected dependency for this plugin ecosystem. | ai | |
| dependencies | unvetted-dep:@commercelayer/cli-ux | AI (dependencies): First-party Commerce Layer CLI UX lib; expected dependency for this plugin ecosystem. | ai | |
| dependencies | unvetted-dep:@commercelayer/cli-core | AI (dependencies): First-party Commerce Layer CLI core lib; expected dependency for this plugin ecosystem. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.9.2 | 10 / 17 | |
| 3.9.1 | 10 / 17 | |
| 3.9.0 | 10 / 18 | |
| 3.8.3 | 10 / 18 | |
| 3.8.2 | 10 / 18 | |
| 3.8.1 | 10 / 18 | |
| 3.8.0 | 10 / 18 | |
| 3.7.6 | 10 / 18 | |
| 3.7.5 | 10 / 18 | |
| 3.7.4 | 10 / 18 | |
| 3.7.3 | 10 / 18 | |
| 3.7.2 | 10 / 18 | |
| 3.7.1 | 10 / 18 | |
| 3.7.0 | 10 / 18 |
v3.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.