anypoint-cli-account-plugin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@oclif/plugin-version | AI (phantom-deps): @oclif/plugin-version is a declared runtime dep used via oclif plugin config, not a direct import; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): MuleSoft org package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 4 / 21 | |
| 1.0.6 | 4 / 21 | |
| 1.0.5 | 4 / 21 | |
| 1.0.4 | 4 / 21 |
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.