← Home

@jh-tech/be-feed-shared

npm

Shared content for the client and server

15
Versions
ISC
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

jackhayes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Absence of Sigstore provenance is common (~88% of npm packages lack it) and is not a meaningful risk signal for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.0.15 3 / 4
0.0.14 3 / 4
0.0.13 3 / 4
0.0.12 3 / 4
0.0.11 3 / 4
0.0.10 3 / 4
0.0.9 3 / 4
0.0.8 3 / 4
0.0.7 3 / 4
0.0.6 3 / 4
0.0.5 3 / 4
0.0.4 3 / 4
0.0.3 3 / 4
0.0.2 3 / 4
0.0.1 3 / 4

v0.0.15

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

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

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

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

1 finding
INFO No provenance attestation provenance

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