← Home

@prosemark/render-html

npm Repository Homepage
8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jsimonrichard

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Scoped package under active development; 0.0.0 reflects pre-release versioning, not throwaway malware pattern. ai
bogus-package bogus-package AI (bogus-package): Missing metadata is consistent with early-stage scoped package, not spam/malware. ai
phantom-deps phantom-dep:@codemirror/state AI (phantom-deps): CodeMirror state is a peer/config dependency; phantom-dep false positive for this package. ai
phantom-deps phantom-dep:@lezer/common AI (phantom-deps): Config-file reference in a legitimate build tool; stable for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.9 6 / 0
0.0.8 5 / 1
0.0.7 5 / 1
0.0.6 5 / 0
0.0.5 5 / 0
0.0.3 5 / 0
0.0.2 5 / 1
0.0.0 5 / 1

v0.0.9

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

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

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

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

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jsimonrichard.

LOW No provenance attestation provenance

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

v0.0.2

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.