← Home

@kb-labs/shared-testing-e2e

npm

E2E test harness for KB Labs platform — kb-dev controller, HTTP/WS/SSE helpers, isolated project roots

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): Internal KB Labs test harness; provenance not enforced for this package scope. 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 2 / 7
2.93.0 2 / 7
2.89.0 2 / 7
2.81.0 2 / 7
2.80.0 2 / 7
2.78.0 2 / 7
2.74.0 2 / 7
2.72.0 2 / 7
2.69.0 2 / 7
2.66.0 2 / 7
2.64.0 2 / 7
2.61.0 2 / 7
2.55.0 2 / 7
2.54.0 2 / 7
2.46.0 2 / 7
2.42.0 2 / 7
2.40.0 2 / 7
2.35.0 2 / 7
2.32.0 2 / 7
2.31.0 2 / 7
2.29.0 2 / 7
2.28.0 2 / 7
2.20.0 2 / 7
2.19.0 2 / 7
2.16.0 2 / 7
2.15.0 2 / 7
2.14.0 2 / 7
2.11.0 2 / 7
2.10.0 2 / 7
2.9.0 2 / 7
2.6.0 2 / 7

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.