@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 33 of 133)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 52 / 60 | |
| 3.10.0 | 52 / 60 | |
| 3.9.3 | 52 / 60 | |
| 3.9.2 | 52 / 60 | |
| 3.9.1 | 52 / 60 | |
| 3.9.0 | 52 / 60 | |
| 3.8.0 | 52 / 60 | |
| 3.7.0 | 52 / 60 | |
| 3.6.1 | 52 / 60 | |
| 3.6.0 | 52 / 60 | |
| 3.5.0 | 52 / 60 | |
| 3.4.2 | 52 / 60 | |
| 3.4.1 | 52 / 60 | |
| 3.4.0 | 51 / 60 | |
| 3.3.6 | 51 / 60 | |
| 3.3.5 | 51 / 60 | |
| 3.3.4 | 51 / 60 | |
| 3.3.3 | 51 / 60 | |
| 3.3.2 | 51 / 60 | |
| 3.3.1 | 51 / 60 | |
| 3.3.0 | 51 / 60 | |
| 3.2.0 | 51 / 59 | |
| 3.1.1 | 51 / 59 | |
| 3.1.0 | 51 / 59 | |
| 3.0.8 | 50 / 59 | |
| 3.0.7 | 50 / 59 | |
| 3.0.6 | 50 / 59 | |
| 3.0.5 | 50 / 59 | |
| 3.0.4 | 50 / 59 | |
| 3.0.3 | 50 / 59 | |
| 3.0.2 | 50 / 59 | |
| 3.0.1 | 50 / 60 | |
| 3.0.0 | 50 / 60 |
v3.10.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.10.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.9.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.9.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.9.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.9.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.8.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.7.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.6.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.6.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.5.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.4.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.4.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.4.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.3.6
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.3.5
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.3.4
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.3.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.3.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.3.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.3.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.2.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.1.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.1.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.0.8
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.0.7
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.0.6
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.0.5
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.0.4
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.0.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.0.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.0.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.0.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.