@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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only signal; no behavioral change vs prior approved version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic official plugin with sporadic release cadence; benign historically. | ai | |
| 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 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 10 / 17 | |
| 4.0.2 | 10 / 17 | |
| 4.0.1 | 10 / 17 | |
| 4.0.0 | 10 / 17 | |
| 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 | |
| 3.6.4 | 10 / 18 | |
| 3.6.3 | 10 / 18 | |
| 3.6.2 | 10 / 18 | |
| 3.6.1 | 10 / 18 | |
| 3.6.0 | 10 / 18 | |
| 3.5.0 | 10 / 18 | |
| 3.4.2 | 10 / 18 | |
| 3.4.1 | 10 / 18 | |
| 3.4.0 | 10 / 18 | |
| 3.3.3 | 10 / 18 | |
| 3.3.2 | 10 / 18 | |
| 3.3.1 | 10 / 18 | |
| 3.3.0 | 10 / 18 | |
| 3.2.1 | 10 / 18 | |
| 3.2.0 | 10 / 18 | |
| 3.1.3 | 9 / 18 | |
| 3.1.1 | 9 / 18 | |
| 3.1.0 | 9 / 18 | |
| 3.0.0 | 9 / 18 |
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (commercelayer.io) than the most recent previously approved version (drpierlu) on 2024-05-30, but commercelayer.io is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: drpierlu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.