← Home

@kb-labs/rest-api-contracts

npm

Shared API contracts for KB Labs REST/CLI/Studio surfaces

50
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

k.baranov

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@kb-labs/studio-contracts AI (dependencies): Dependency is a local monorepo link: path, not a real npm package; no supply-chain risk. ai
provenance no-provenance AI (provenance): Established package with clean history; lack of Sigstore provenance is a process gap, not a security indicator. ai

Versions (showing 50 of 50)

Version Deps Published
2.107.0 2 / 6
2.106.0 2 / 6
2.105.0 2 / 6
2.104.0 2 / 6
2.103.0 2 / 6
2.102.0 2 / 6
2.101.0 2 / 6
2.100.0 2 / 6
2.98.0 2 / 6
2.96.0 2 / 6
2.94.0 2 / 6
2.93.0 2 / 6
2.89.0 2 / 6
2.88.0 2 / 6
2.87.0 2 / 6
2.81.0 2 / 6
2.80.0 2 / 6
2.79.0 2 / 6
2.66.0 2 / 6
2.65.0 2 / 6
2.64.0 2 / 6
2.61.0 2 / 6
2.60.0 2 / 6
2.54.0 2 / 6
2.46.0 2 / 6
2.45.0 2 / 6
2.43.0 2 / 6
2.38.0 2 / 6
2.35.0 2 / 6
2.32.0 2 / 6
2.31.0 2 / 6
2.28.0 2 / 6
2.23.0 2 / 6
2.22.0 2 / 6
2.20.0 2 / 6
2.18.0 2 / 6
2.17.0 2 / 6
2.15.0 2 / 6
2.13.0 2 / 6
2.12.0 2 / 6
2.11.0 2 / 6
2.9.0 2 / 6
2.6.0 2 / 6
1.6.0 2 / 6
1.5.0 2 / 6
1.4.0 2 / 6
1.3.0 2 / 6
1.2.0 2 / 6
1.1.0 2 / 6
1.0.0 2 / 6

v2.107.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.106.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.105.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.104.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.103.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.102.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.101.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.100.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.98.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.96.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.