@kb-labs/studio-data-client
KB Labs Studio data client — API SDK with versioned contracts, mocks, and TanStack Query hooks
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/qa-contracts | AI (phantom-deps): Same-org scoped dep; likely type-only or re-exported import not caught by static analysis. | ai | |
| phantom-deps | phantom-dep:@kb-labs/agent-contracts | AI (phantom-deps): Same-org scoped dep; likely type-only or re-exported import not caught by static analysis. | ai | |
| phantom-deps | phantom-dep:@kb-labs/commit-contracts | AI (phantom-deps): Same-org scoped dep; likely type-only or re-exported import not caught by static analysis. | ai | |
| phantom-deps | phantom-dep:@kb-labs/quality-contracts | AI (phantom-deps): Same-org scoped dep; likely type-only or re-exported import not caught by static analysis. | ai | |
| phantom-deps | phantom-dep:@kb-labs/release-manager-contracts | AI (phantom-deps): Same-org scoped dep; likely type-only or re-exported import not caught by static analysis. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 13 / 9 | |
| 2.93.0 | 13 / 9 | |
| 2.89.0 | 13 / 9 | |
| 2.9.0 | 13 / 9 | |
| 2.6.0 | 13 / 9 | |
| 0.7.0 | 13 / 9 | |
| 0.6.0 | 13 / 9 | |
| 0.5.0 | 13 / 9 | |
| 0.4.0 | 13 / 9 | |
| 0.3.0 | 13 / 9 | |
| 0.2.0 | 13 / 9 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.