@platejs/docx-io
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:validator | AI (phantom-deps): validator is a declared runtime dependency; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:react-compiler-runtime | AI (phantom-deps): react-compiler-runtime is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 53.0.8 | 13 / 2 | |
| 53.0.0 | 13 / 2 | |
| 52.3.10 | 13 / 2 | |
| 52.3.8 | 13 / 1 | |
| 52.3.6 | 13 / 1 | |
| 52.2.0 | 13 / 3 |
v53.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v53.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v52.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.