rich-text-editor
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/rich-text-editor-bundle.js | AI (source-diff): Encoded strings are Unicode escapes in MathQuill bundled library documentation — not obfuscation. | ai | |
| phantom-deps | phantom-dep:jquery | AI (phantom-deps): jQuery is a declared peer dependency loaded by convention, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@types/jquery | AI (phantom-deps): Type-only package; framework-scoped, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/sanitize-html | AI (phantom-deps): Type-only package; framework-scoped, stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 8.11.2 | 7 / 25 | |
| 8.11.0 | 7 / 25 | |
| 8.10.5 | 7 / 25 | |
| 8.10.4 | 7 / 25 | |
| 8.10.3 | 7 / 25 | |
| 8.10.2 | 7 / 25 | |
| 8.10.1 | 7 / 25 | |
| 8.10.0 | 7 / 25 | |
| 8.9.1 | 7 / 25 | |
| 8.9.0 | 7 / 25 |
v8.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.11.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.