prosemirror-state
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:prosemirror-view | AI (dependencies): prosemirror-view is a first-party ProseMirror package by the same author (marijn); unvetted flag is a false positive for this ecosystem. | ai | |
| dependencies | unvetted-dep:prosemirror-model | AI (dependencies): prosemirror-model is a first-party ProseMirror package by the same author (marijn); unvetted flag is a false positive for this ecosystem. | ai | |
| dependencies | unvetted-dep:prosemirror-transform | AI (dependencies): prosemirror-transform is a first-party ProseMirror package by the same author (marijn); unvetted flag is a false positive for this ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; absence is expected and not a risk signal for this publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.4.4 | 3 / 2 | |
| 1.4.3 | 3 / 2 | |
| 1.4.2 | 3 / 2 | |
| 1.4.1 | 2 / 2 | |
| 1.4.0 | 2 / 2 | |
| 1.3.4 | 2 / 5 | |
| 1.3.3 | 2 / 5 | |
| 1.3.2 | 2 / 5 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 1.2.4 | 2 / 5 | |
| 1.2.3 | 2 / 5 | |
| 1.2.2 | 2 / 5 | |
| 1.2.1 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.1 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.2 | 2 / 5 | |
| 1.0.1 | 2 / 5 | |
| 1.0.0 | 2 / 5 |
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.