← Home

@kb-labs/rest-api-core

npm

Core REST API functionality for KB Labs, including request handling and routing

42
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
provenance no-provenance AI (provenance): Established package with clean history; lack of Sigstore attestation is a process gap, not a security indicator. ai

Versions (showing 42 of 42)

Version Deps Published
2.109.0 5 / 6
2.107.0 5 / 6
2.106.0 5 / 6
2.105.0 5 / 6
2.104.0 5 / 6
2.103.0 5 / 6
2.102.0 5 / 6
2.101.0 5 / 6
2.100.0 5 / 6
2.98.0 5 / 6
2.96.0 5 / 6
2.94.0 5 / 6
2.93.0 5 / 6
2.89.0 5 / 6
2.87.0 5 / 6
2.80.0 5 / 6
2.75.0 5 / 6
2.72.0 5 / 6
2.68.0 5 / 6
2.61.0 5 / 6
2.59.0 5 / 6
2.53.0 5 / 6
2.47.0 5 / 6
2.46.0 5 / 6
2.41.0 5 / 6
2.38.0 5 / 6
2.35.0 5 / 6
2.33.0 5 / 6
2.28.0 5 / 6
2.22.0 5 / 6
2.19.0 5 / 6
2.18.0 5 / 6
2.12.0 5 / 6
2.9.0 5 / 6
2.6.0 5 / 6
1.6.0 5 / 6
1.5.0 5 / 6
1.4.0 5 / 6
1.3.0 5 / 6
1.2.0 5 / 6
1.1.0 5 / 6
1.0.0 5 / 6

v2.109.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.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.