← Home

@readme/oas-to-har

npm Repository Homepage
52
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

gkobergerdomharringtonmjcuvajonursenbachrafegoldbergdarrenyong

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established ReadmeIO monorepo package with clear GitHub repository link; lack of Sigstore provenance is not a meaningful risk signal here. ai

Versions (showing 52 of 52)

Version Deps Published
38.0.0 4 / 7
37.2.0 4 / 7
37.0.0 4 / 7
36.0.0 4 / 7
34.0.2 4 / 7
34.0.1 4 / 7
34.0.0 4 / 7
33.1.7 4 / 7
33.1.6 4 / 7
33.1.2 4 / 7
33.1.1 4 / 7
33.1.0 4 / 7
33.0.0 4 / 7
32.1.15 4 / 7
32.1.14 4 / 7
32.1.13 4 / 7
32.1.12 4 / 7
31.0.15 4 / 7
31.0.14 4 / 7
31.0.13 4 / 7
31.0.12 4 / 7
31.0.11 4 / 7
31.0.10 4 / 7
31.0.9 4 / 7
31.0.8 4 / 7
31.0.7 4 / 7
31.0.6 4 / 7
31.0.5 4 / 7
31.0.4 4 / 7
31.0.3 4 / 7
31.0.2 4 / 7
31.0.1 4 / 7
31.0.0 4 / 7
30.0.3 4 / 7
30.0.2 4 / 7
30.0.0 4 / 7
28.0.8 4 / 7
28.0.7 4 / 7
28.0.6 4 / 7
28.0.5 4 / 7
28.0.4 4 / 7
28.0.3 4 / 7
28.0.2 4 / 7
28.0.1 4 / 7
28.0.0 4 / 7
27.3.3 4 / 7
27.3.2 4 / 7
27.3.1 4 / 7
27.3.0 4 / 7
27.2.2 4 / 7
27.2.1 4 / 7
27.2.0 4 / 7

v38.0.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.

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