@kb-labs/sdk
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): zod is a widely-trusted validation library; not a supply-chain risk for this package. | ai | |
| dependencies | unvetted-dep:@kb-labs/studio-contracts | AI (dependencies): Local monorepo link: dependency; not a real npm dep, stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 32 approved dependents; lack of Sigstore attestation is a process gap, not a security signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.21.2 | 1 / 23 | |
| 2.20.1 | 1 / 7 | |
| 2.18.1 | 15 / 7 | |
| 1.6.6 | 15 / 7 | |
| 1.6.5 | 15 / 7 | |
| 1.6.1 | 15 / 7 | |
| 1.6.0 | 15 / 7 | |
| 1.5.0 | 14 / 7 | |
| 1.4.0 | 14 / 7 | |
| 1.3.0 | 14 / 7 | |
| 1.2.0 | 14 / 7 | |
| 1.0.0 | 10 / 7 |
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
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.18.1
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.
v1.6.6
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.
v1.6.5
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.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.