anypoint-cli-command
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json from main module path for project name — not arbitrary module loading. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT payload parsing (split on '.', decode middle segment) — not obfuscated payload execution. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Declared as oclif plugin in oclif config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-version | AI (phantom-deps): Declared as oclif plugin in oclif config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:clone | AI (phantom-deps): Likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Used via apollo-client ecosystem; indirect usage pattern common here. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Proxy agent likely configured at runtime; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.6.8 | 23 / 24 | |
| 1.6.7 | 23 / 24 | |
| 1.6.6 | 23 / 24 | |
| 1.6.5 | 23 / 24 | |
| 1.6.3 | 23 / 24 | |
| 1.6.2 | 23 / 24 | |
| 1.6.1 | 23 / 24 | |
| 1.6.0 | 23 / 24 |
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.