prosemirror-changeset
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established ProseMirror package by Marijn Haverbeke; lack of Sigstore provenance is common and not a risk signal for this well-known author. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 1 / 4 | |
| 2.4.0 | 1 / 4 | |
| 2.3.1 | 1 / 4 | |
| 2.3.0 | 1 / 4 | |
| 2.2.1 | 1 / 3 | |
| 2.2.0 | 1 / 3 | |
| 2.1.2 | 1 / 8 | |
| 2.1.1 | 1 / 8 | |
| 2.1.0 | 1 / 8 | |
| 2.0.4 | 1 / 8 | |
| 2.0.3 | 1 / 8 | |
| 2.0.2 | 1 / 8 | |
| 2.0.1 | 1 / 8 | |
| 2.0.0 | 1 / 8 |
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.