anypoint-cli-runtime-mgr-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:@types/semver | AI (phantom-deps): Type-only package used by TypeScript toolchain, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-version | AI (phantom-deps): Referenced in oclif config (plugins array), not a direct code import — expected pattern for oclif plugins. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 9 / 21 | |
| 1.0.8 | 7 / 21 | |
| 1.0.5 | 7 / 21 | |
| 1.0.4 | 7 / 21 | |
| 1.0.3 | 7 / 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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.