@mdxeditor/editor
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:@radix-ui/react-icons | AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this component library. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across all prior versions and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-popper | AI (dependencies): @radix-ui/react-popper is a well-known Radix UI primitive; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 277 versions published over package lifetime; SLSA provenance confirms CI/CD pipeline; not a dormant account. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-popper | AI (phantom-deps): Radix UI sub-package; likely consumed transitively or via dynamic patterns not detected statically. | ai | |
| phantom-deps | phantom-dep:unidiff | AI (phantom-deps): Listed in package.json dependencies; likely bundled into dist output by vite build. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toggle-group | AI (phantom-deps): Radix UI sub-package; likely consumed transitively or via dynamic patterns not detected statically. | ai | |
| phantom-deps | phantom-dep:@radix-ui/colors | AI (phantom-deps): CSS design tokens package; likely consumed via CSS imports not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:@lexical/clipboard | AI (phantom-deps): Lexical sub-package likely used indirectly or bundled; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lexical/plain-text | AI (phantom-deps): Lexical sub-package likely used indirectly or bundled; stable false positive for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 55 / 61 | |
| 3.55.0 | 56 / 61 | |
| 3.54.1 | 56 / 61 | |
| 3.54.0 | 56 / 61 | |
| 3.53.0 | 56 / 61 | |
| 3.52.5 | 56 / 61 | |
| 3.52.3 | 56 / 61 | |
| 3.52.2 | 56 / 60 | |
| 3.52.0 | 56 / 60 | |
| 3.51.0 | 56 / 60 | |
| 3.50.0 | 56 / 60 | |
| 3.49.3 | 56 / 60 | |
| 3.49.1 | 56 / 60 | |
| 3.47.0 | 56 / 60 | |
| 3.46.0 | 56 / 60 | |
| 3.45.0 | 56 / 60 | |
| 3.44.2 | 56 / 60 | |
| 3.41.0 | 54 / 60 | |
| 3.40.1 | 54 / 60 | |
| 3.39.1 | 54 / 60 | |
| 3.39.0 | 54 / 60 | |
| 3.36.0 | 54 / 60 | |
| 3.35.1 | 54 / 60 | |
| 3.35.0 | 54 / 60 | |
| 3.34.0 | 54 / 60 | |
| 3.32.3 | 53 / 60 | |
| 3.32.2 | 53 / 60 | |
| 3.32.1 | 53 / 60 | |
| 3.32.0 | 53 / 60 | |
| 3.31.1 | 53 / 60 |
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.54.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.52.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.52.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.52.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.44.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.