@manuscripts/body-editor
Prosemirror components for editing and viewing manuscripts
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package with consistent publish history; lack of Sigstore provenance is not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:csl-json | AI (phantom-deps): csl-json is a type-alias dev dep (@types/csl aliased to csl-json); not a real runtime import gap. | ai | |
| phantom-deps | phantom-dep:mathjax | AI (phantom-deps): mathjax is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): react-is is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.12.47 | 43 / 37 | |
| 3.12.34 | 43 / 43 | |
| 3.9.11 | 46 / 43 | |
| 3.8.5 | 46 / 43 | |
| 3.7.0 | 46 / 40 | |
| 3.2.18 | 46 / 40 | |
| 3.2.2 | 46 / 40 | |
| 3.0.2 | 46 / 40 |
v3.12.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.