slate-react
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 |
|---|---|---|---|---|
| source-diff | net-exec-file-transition:dist/slate-react.min.js | AI (source-diff): Minified build of same UMD bundle; no fetch/exec payload. | ai | |
| source-diff | net-exec-file-transition:dist/slate-react.js | AI (source-diff): Rollup UMD build output; heuristic net+exec match on bundle, no actual dropper behavior. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): slate-dev-warning is a first-party sibling package in the same monorepo. | ai | |
| phantom-deps | phantom-dep:keycode | AI (phantom-deps): Used in transpiled lib/ build output; heuristic misses it due to minification. | ai | |
| source-diff | bulk-obfuscated-files:lib | AI (source-diff): Routine transpiled build output under lib/, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:is-window | AI (phantom-deps): Legitimate small utility dep for DOM checks; likely used but not import-scannable. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Declared dependency; used transitively in slate-react codebase. | ai | |
| phantom-deps | phantom-dep:is-plain-object | AI (phantom-deps): Declared dependency; used transitively in slate-react codebase. | ai | |
| phantom-deps | phantom-dep:is-hotkey | AI (phantom-deps): Declared dependency; used transitively in slate-react codebase. | ai |
Versions (showing 90 of 290)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 15 / 5 | |
| 0.14.3 | 15 / 5 | |
| 0.14.2 | 15 / 5 | |
| 0.14.1 | 15 / 5 | |
| 0.14.0 | 15 / 5 | |
| 0.13.4 | 15 / 5 | |
| 0.13.3 | 15 / 5 | |
| 0.13.2 | 15 / 5 | |
| 0.13.1 | 15 / 5 | |
| 0.13.0 | 15 / 5 | |
| 0.12.11 | 15 / 5 | |
| 0.12.10 | 15 / 5 | |
| 0.12.9 | 15 / 5 | |
| 0.12.8 | 15 / 5 | |
| 0.12.7 | 15 / 5 | |
| 0.12.6 | 15 / 5 | |
| 0.12.5 | 15 / 4 | |
| 0.12.4 | 15 / 4 | |
| 0.12.3 | 15 / 4 | |
| 0.12.2 | 15 / 4 | |
| 0.12.1 | 15 / 4 | |
| 0.12.0 | 15 / 4 | |
| 0.11.6 | 15 / 4 | |
| 0.11.5 | 15 / 4 | |
| 0.11.4 | 15 / 4 | |
| 0.11.3 | 15 / 4 | |
| 0.11.2 | 15 / 7 | |
| 0.11.1 | 15 / 7 | |
| 0.11.0 | 15 / 7 | |
| 0.10.23 | 15 / 7 | |
| 0.10.22 | 15 / 7 | |
| 0.10.21 | 15 / 7 | |
| 0.10.20 | 15 / 7 | |
| 0.10.19 | 15 / 7 | |
| 0.10.18 | 14 / 7 | |
| 0.10.17 | 14 / 7 | |
| 0.10.16 | 14 / 7 | |
| 0.10.15 | 14 / 7 | |
| 0.10.14 | 14 / 7 | |
| 0.10.13 | 14 / 7 | |
| 0.10.12 | 14 / 7 | |
| 0.10.11 | 14 / 7 | |
| 0.10.10 | 14 / 7 | |
| 0.10.9 | 14 / 7 | |
| 0.10.8 | 14 / 7 | |
| 0.10.7 | 14 / 7 | |
| 0.10.6 | 14 / 7 | |
| 0.10.5 | 14 / 7 | |
| 0.10.4 | 14 / 7 | |
| 0.10.3 | 14 / 7 | |
| 0.10.2 | 14 / 7 | |
| 0.10.1 | 14 / 7 | |
| 0.10.0 | 14 / 7 | |
| 0.9.1 | 14 / 7 | |
| 0.9.0 | 14 / 7 | |
| 0.8.2 | 14 / 7 | |
| 0.8.1 | 14 / 7 | |
| 0.8.0 | 14 / 7 | |
| 0.7.4 | 14 / 7 | |
| 0.7.3 | 14 / 7 | |
| 0.7.2 | 14 / 7 | |
| 0.7.1 | 14 / 7 | |
| 0.7.0 | 14 / 7 | |
| 0.6.0 | 14 / 7 | |
| 0.5.5 | 14 / 7 | |
| 0.5.4 | 14 / 7 | |
| 0.5.3 | 14 / 7 | |
| 0.5.2 | 13 / 7 | |
| 0.5.1 | 13 / 7 | |
| 0.5.0 | 13 / 7 | |
| 0.4.0 | 13 / 7 | |
| 0.3.4 | 13 / 7 | |
| 0.3.3 | 13 / 7 | |
| 0.3.2 | 13 / 7 | |
| 0.3.1 | 13 / 7 | |
| 0.3.0 | 13 / 7 | |
| 0.2.2 | 12 / 7 | |
| 0.2.1 | 12 / 7 | |
| 0.2.0 | 12 / 7 | |
| 0.1.10 | 12 / 7 | |
| 0.1.9 | 12 / 7 | |
| 0.1.8 | 12 / 7 | |
| 0.1.7 | 12 / 7 | |
| 0.1.6 | 12 / 7 | |
| 0.1.5 | 12 / 7 | |
| 0.1.4 | 12 / 7 | |
| 0.1.3 | 12 / 7 | |
| 0.1.2 | 12 / 7 | |
| 0.1.1 | 12 / 7 | |
| 0.1.0 | 12 / 7 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.