← Home

prism-react-renderer

npm Repository Homepage

Renders highlighted Prism output using React

26
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

michaelmerrillsarmeyermariano-formidableryan.roemerformidable-ownerformidablelabscarbonrobotmasiddeescott-rippeysarahformidablerobwalkercoceceppakeithluchtelscottianstewartphilpl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs `patch-package`, a well-known utility for applying local patches. No remote code execution or exfiltration risk; stable pattern for this package. ai
provenance publisher-changed AI (provenance): Publisher changed to jpdriver (Formidable Labs), a well-known React ecosystem org with 393 approved packages and 0 rejected. Consistent with a legitimate organizational takeover. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Formidable Labs employees/accounts, consistent with the org taking over stewardship of this package. Not indicative of compromise. ai

Versions (showing 26 of 26)

Version Deps Published
2.4.1 2 / 23
2.4.0 2 / 23
2.3.1 2 / 23
2.3.0 2 / 23
2.2.0 2 / 23
2.1.0 2 / 23
2.0.6 2 / 23
2.0.5 2 / 23
2.0.4 2 / 23
2.0.3 2 / 23
2.0.2 2 / 23
2.0.1 2 / 23
2.0.0 1 / 24
1.3.5 0 / 30
1.3.4 0 / 30
1.3.3 0 / 30
1.3.2 0 / 30
1.3.1 0 / 30
1.3.0 0 / 30
1.2.1 0 / 28
1.2.0 0 / 28
1.1.1 0 / 29
1.1.0 0 / 29
1.0.2 0 / 26
1.0.1 0 / 26
1.0.0 0 / 26

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

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

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

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

v2.1.0

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.0.6

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.0.5

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.0.4

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.0.3

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.0.2

1 finding
INFO Has SLSA provenance attestation provenance

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

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

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

v1.3.5

2 findings
HIGH Publisher changed: philpl → gksander (on 2022-06-30) provenance

This version was published by a different npm account than previous versions on 2022-06-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.3.4

2 findings
HIGH Publisher changed: philpl → gksander (on 2022-06-30) provenance

This version was published by a different npm account than previous versions on 2022-06-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.3.3

2 findings
HIGH Publisher changed: philpl → jpdriver (on 2022-05-16) provenance

This version was published by a different npm account than previous versions on 2022-05-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.3.2

2 findings
HIGH Publisher changed: philpl → jpdriver (on 2022-05-16) provenance

This version was published by a different npm account than previous versions on 2022-05-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.3.1

2 findings
HIGH Publisher changed: philpl → jpdriver (on 2022-02-09) provenance

This version was published by a different npm account than previous versions on 2022-02-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.3.0

3 findings
HIGH Package has 'postinstall' script install-scripts

Script: patch-package

HIGH Publisher changed: philpl → jpdriver (on 2022-02-08) provenance

This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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