@cloudbase/manager-node
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Fires in scripts/link.js (dev symlink helper), not in published lib output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cloudbase/database | AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 5.5.1 | 15 / 17 | |
| 5.4.0 | 15 / 17 | |
| 5.3.0 | 14 / 16 | |
| 5.2.0 | 14 / 16 | |
| 5.1.1 | 14 / 16 | |
| 5.1.0 | 14 / 16 | |
| 5.0.2 | 14 / 16 | |
| 5.0.0 | 14 / 16 | |
| 4.10.6 | 13 / 16 | |
| 4.10.5 | 13 / 16 | |
| 4.10.4 | 13 / 16 | |
| 4.10.3 | 13 / 16 | |
| 4.10.2 | 13 / 16 | |
| 4.10.1 | 13 / 16 | |
| 4.10.0 | 13 / 16 | |
| 4.9.0 | 13 / 16 | |
| 4.8.0 | 13 / 16 | |
| 4.7.5 | 13 / 16 | |
| 4.7.4 | 13 / 16 | |
| 4.7.3 | 13 / 16 | |
| 4.7.2 | 13 / 16 | |
| 4.7.1 | 13 / 16 | |
| 4.7.0 | 13 / 16 | |
| 4.6.9 | 13 / 16 | |
| 4.6.8 | 13 / 16 | |
| 4.6.7 | 13 / 16 | |
| 4.6.6 | 13 / 16 |
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.