← Home

@pear-protocol/utils

npm

Pear Protocol Utility functions

25
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

coinlorddlitmarvgpsxtremehan-pear

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Young protocol package; provenance absence is common and no other risk signals present. ai

Versions (showing 25 of 25)

Version Deps Published
0.2.0 3 / 4
0.1.0 3 / 4
0.0.23 2 / 4
0.0.22 2 / 4
0.0.21 2 / 4
0.0.20 2 / 4
0.0.19 2 / 4
0.0.18 2 / 4
0.0.17 2 / 4
0.0.16 2 / 3
0.0.15 2 / 3
0.0.14 2 / 3
0.0.13 2 / 3
0.0.12 2 / 3
0.0.11 2 / 3
0.0.10 2 / 3
0.0.9 2 / 3
0.0.8 2 / 3
0.0.7 2 / 3
0.0.6 2 / 3
0.0.5 2 / 3
0.0.4 2 / 3
0.0.3 2 / 3
0.0.2 2 / 3
0.0.1 2 / 3

v0.2.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.1.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.0.23

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.0.22

1 finding
INFO No provenance attestation provenance

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