← Home

@agent-facets/cli-linux-x64

13
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

jimadorjuliancoy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): CircleCI-published platform binary; provenance not yet enabled for this package family. ai
npm-metadata no-description AI (npm-metadata): Platform-specific optional dep shards routinely omit descriptions. ai
bogus-package bogus-package AI (bogus-package): Platform-specific binary distribution package; sparse metadata and tiny payload are structural, not spam indicators. ai

Versions (showing 13 of 13)

Version Deps Published
0.25.0 0 / 0
0.24.1 0 / 0
0.24.0 0 / 0
0.23.0 0 / 0
0.22.3 0 / 0
0.22.2 0 / 0
0.22.0 0 / 0
0.21.1 0 / 0
0.18.2 0 / 0
0.16.0 0 / 0
0.14.0 0 / 0
0.7.3 0 / 0
0.0.1 0 / 0

v0.25.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.

v0.24.1

1 finding
INFO No provenance attestation provenance

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

v0.24.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.

v0.23.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.

v0.22.3

1 finding
INFO No provenance attestation provenance

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

v0.22.2

1 finding
INFO No provenance attestation provenance

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

v0.22.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.