@cloudbase/adapter-interface
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale publisher change with clean history and no code changes; consistent with legitimate org handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same handoff; no takeover indicators. | ai | |
| provenance | publisher-changed-stale | AI (provenance): 460 days live on npm without unpublish is inconsistent with compromise. | ai |
v0.7.0
2 findingsThis version was published by a different npm account (areo-joe) than the most recent previously approved version (binggg) on 2025-04-14. It has since remained available on npm for 460 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.