@kb-labs/core-tenant
Multi-tenancy primitives for KB Labs
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an internal @kb-labs scoped package pinned to the same version, consistent with monorepo coordinated releases. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 305 approved packages; lack of Sigstore attestation is a process gap, not a security signal for this package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 1 / 6 | |
| 2.93.0 | 1 / 6 | |
| 2.89.0 | 1 / 6 | |
| 2.88.0 | 1 / 6 | |
| 2.82.0 | 1 / 6 | |
| 2.81.0 | 1 / 6 | |
| 2.80.0 | 1 / 6 | |
| 2.79.0 | 1 / 6 | |
| 2.78.0 | 1 / 6 | |
| 2.75.0 | 1 / 6 | |
| 2.74.0 | 1 / 6 | |
| 2.73.0 | 1 / 6 | |
| 2.72.0 | 1 / 6 | |
| 2.68.0 | 1 / 6 | |
| 2.67.0 | 1 / 6 | |
| 2.66.0 | 1 / 6 | |
| 2.65.0 | 1 / 6 | |
| 2.64.0 | 1 / 6 | |
| 2.63.0 | 1 / 6 | |
| 2.62.0 | 1 / 6 | |
| 2.61.0 | 1 / 6 | |
| 2.59.0 | 1 / 6 | |
| 2.58.0 | 1 / 6 | |
| 2.56.0 | 1 / 6 | |
| 2.55.0 | 1 / 6 | |
| 2.54.0 | 1 / 6 | |
| 2.47.0 | 1 / 6 | |
| 2.46.0 | 1 / 6 | |
| 2.43.0 | 1 / 6 | |
| 2.41.0 | 1 / 6 | |
| 2.40.0 | 1 / 6 | |
| 2.39.0 | 1 / 6 | |
| 2.38.0 | 1 / 6 | |
| 2.37.0 | 1 / 6 | |
| 2.36.0 | 1 / 6 | |
| 2.35.0 | 1 / 6 | |
| 2.34.0 | 1 / 6 | |
| 2.32.0 | 1 / 6 | |
| 2.31.0 | 1 / 6 | |
| 2.30.0 | 1 / 6 | |
| 2.28.0 | 1 / 6 | |
| 2.25.0 | 1 / 6 | |
| 2.23.0 | 1 / 6 | |
| 2.20.0 | 1 / 6 | |
| 2.19.0 | 1 / 6 | |
| 2.18.0 | 1 / 6 | |
| 2.17.0 | 1 / 6 | |
| 2.16.0 | 1 / 6 | |
| 2.14.0 | 1 / 6 | |
| 2.12.0 | 1 / 6 | |
| 2.11.0 | 1 / 6 |
v2.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
1 finding[Accepted risk] 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.88.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.82.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.81.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.80.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.79.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.78.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.75.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.74.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.73.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.72.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.68.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.67.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.66.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.65.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.64.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.63.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.62.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.61.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.59.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.58.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.56.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.55.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.54.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.47.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.46.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.43.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.41.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.40.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.39.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.38.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.37.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.36.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.35.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.34.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.32.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.31.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.30.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.28.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.25.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.23.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.20.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.19.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.18.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.17.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.16.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.14.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.12.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.11.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.