@plone/volto-slate
Slate.js integration with Volto
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:weak-key | AI (dependencies): weak-key is a small, benign WeakMap utility; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:redux-mock-store | AI (dependencies): redux-mock-store is a well-known testing utility; no malicious history, stable false positive. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): jsdom is a declared runtime dep used in SSR/config context; phantom-dep heuristic fires but it's legitimately referenced. | ai | |
| phantom-deps | phantom-dep:weak-key | AI (phantom-deps): Declared dep used indirectly via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:slate-history | AI (phantom-deps): Declared dep used indirectly via config; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Plone/Volto ecosystem package; README and metadata signals are false positives. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 19.0.4 | 20 / 4 | |
| 19.0.3 | 20 / 4 | |
| 19.0.2 | 20 / 4 | |
| 19.0.1 | 20 / 3 | |
| 19.0.0 | 20 / 3 | |
| 18.10.1 | 19 / 5 | |
| 18.10.0 | 19 / 4 | |
| 18.9.2 | 19 / 4 | |
| 18.9.1 | 19 / 4 | |
| 18.9.0 | 20 / 3 | |
| 18.8.1 | 20 / 3 | |
| 18.8.0 | 20 / 3 | |
| 18.7.1 | 20 / 3 | |
| 18.7.0 | 20 / 3 | |
| 18.6.0 | 20 / 3 | |
| 18.5.1 | 20 / 3 | |
| 18.5.0 | 20 / 3 | |
| 18.4.0 | 20 / 3 | |
| 18.3.1 | 20 / 3 | |
| 18.3.0 | 20 / 3 | |
| 18.2.3 | 20 / 3 | |
| 18.2.2 | 20 / 3 | |
| 18.2.1 | 22 / 3 | |
| 18.2.0 | 22 / 3 | |
| 18.1.0 | 22 / 3 | |
| 18.0.4 | 22 / 3 | |
| 18.0.3 | 22 / 3 | |
| 18.0.2 | 22 / 3 | |
| 18.0.1 | 22 / 3 | |
| 18.0.0 | 22 / 3 |
v19.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.