prosemirror-history
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rope-sequence | AI (dependencies): rope-sequence is a legitimate ProseMirror ecosystem dependency maintained by the same author; stable for this package. | ai | |
| dependencies | unvetted-dep:prosemirror-view | AI (dependencies): prosemirror-view is a core ProseMirror package by the same author; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:prosemirror-state | AI (dependencies): prosemirror-state is a core ProseMirror package by the same author; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:prosemirror-transform | AI (dependencies): prosemirror-transform is a core ProseMirror package by the same author; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-view | AI (phantom-deps): prosemirror-view is used for integration/type purposes in ProseMirror plugins without direct import; expected pattern for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 4 / 2 | |
| 1.4.1 | 4 / 2 | |
| 1.4.0 | 4 / 2 | |
| 1.3.2 | 4 / 2 | |
| 1.3.1 | 4 / 2 | |
| 1.3.0 | 3 / 2 | |
| 1.2.0 | 3 / 6 | |
| 1.1.3 | 3 / 6 | |
| 1.1.2 | 3 / 6 | |
| 1.1.1 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.4 | 3 / 6 | |
| 1.0.3 | 3 / 6 | |
| 1.0.2 | 3 / 6 | |
| 1.0.1 | 3 / 6 | |
| 1.0.0 | 3 / 6 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.