react-shiki
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Runtime utility for conditional CSS classes; legitimately used in React component. | ai | |
| phantom-deps | phantom-dep:dequal | AI (phantom-deps): Runtime equality check utility; legitimately used in component logic. | ai | |
| phantom-deps | phantom-dep:hast-util-to-jsx-runtime | AI (phantom-deps): Runtime AST-to-JSX converter; core to syntax-highlighter functionality. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Type definitions loaded by test framework convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:unist-util-visit | AI (phantom-deps): Build/config tooling; not a runtime concern for consumers. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 5 / 14 | |
| 0.10.0 | 5 / 14 | |
| 0.9.3 | 5 / 11 | |
| 0.9.2 | 5 / 11 | |
| 0.9.1 | 5 / 11 | |
| 0.9.0 | 5 / 11 | |
| 0.8.0 | 5 / 11 | |
| 0.7.4 | 5 / 12 | |
| 0.7.3 | 6 / 11 | |
| 0.7.2 | 6 / 11 | |
| 0.7.1 | 6 / 11 | |
| 0.7.0 | 6 / 11 | |
| 0.6.0 | 6 / 11 |
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.