← Home

@kb-labs/agent-tools

npm

Agent management tools for planning, coordination, and execution

38
Versions
MIT
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

Keywords

agentscoordinationkb-labsplanningtools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package with 70 versions; lack of Sigstore attestation is not a disqualifier here. ai

Versions (showing 38 of 38)

Version Deps Published
2.110.0 5 / 6
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 4 / 6
2.88.0 4 / 6
2.77.0 4 / 6
2.75.0 4 / 6
2.69.0 4 / 6
2.66.0 4 / 6
2.65.0 4 / 6
2.57.0 4 / 6
2.47.0 4 / 6
2.46.0 4 / 6
2.42.0 4 / 6
2.41.0 4 / 6
2.40.0 4 / 6
2.38.0 4 / 6
2.28.0 4 / 6
2.14.0 4 / 6
2.13.0 4 / 6
2.9.0 4 / 6
2.6.0 4 / 6
0.6.0 4 / 6
0.5.0 4 / 6
0.4.0 4 / 6
0.3.0 4 / 6
0.2.0 4 / 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.