@kb-labs/release-manager-checks
KB Labs Release Manager - check adapters for audit, devlink, mind, tests, and build
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@kb-labs/plugin-contracts | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on transitive/type-only imports in bundled packages. | ai | |
| phantom-deps | phantom-dep:@kb-labs/release-manager-core | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on transitive/type-only imports in bundled packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 2 / 7 | |
| 2.93.0 | 2 / 7 | |
| 2.89.0 | 2 / 7 | |
| 2.9.0 | 2 / 7 | |
| 2.6.0 | 2 / 7 | |
| 0.6.0 | 2 / 7 |
v2.94.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.