prosemirror-model
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:orderedmap | AI (dependencies): orderedmap is a stable ProseMirror ecosystem package by the same author (Marijn Haverbeke); it is a long-standing, intentional dependency of prosemirror-model. | ai | |
| provenance | no-provenance | AI (provenance): prosemirror-model is a mature, well-established package by a trusted publisher; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.25.7 | 1 / 3 | |
| 1.25.6 | 1 / 3 | |
| 1.25.5 | 1 / 3 | |
| 1.25.4 | 1 / 3 | |
| 1.25.3 | 1 / 3 | |
| 1.25.2 | 1 / 3 |
v1.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.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.
v1.25.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.