← Home

are-docs-informative

Checks whether a documentation description introduces any new information. ℹ️

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

joshuakgoldberg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Version 0.0.0 is the legitimate initial release from a well-established, trusted publisher (joshuakgoldberg) with 591 approved packages. Not indicative of malicious intent. ai
provenance no-provenance AI (provenance): Package predates widespread Sigstore provenance adoption; no provenance is common and not a risk signal for this well-established publisher. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.1 0 / 34
0.1.0 0 / 34
0.0.2 0 / 36
0.0.1 0 / 36
0.0.0 0 / 35

v0.1.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.