← Home

@kb-labs/core-tenant

npm

Multi-tenancy primitives for KB Labs

51
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
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 75)

View all versions
Version Deps Published
2.110.0 1 / 6
2.109.0 1 / 6
2.107.0 1 / 6
2.106.0 1 / 6
2.105.0 1 / 6
2.104.0 1 / 6
2.103.0 1 / 6
2.102.0 1 / 6
2.101.0 1 / 6
2.100.0 1 / 6
2.98.0 1 / 6
2.96.0 1 / 6
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

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