prosemirror-markdown
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is Marijn Haverbeke, the original ProseMirror author with a long, trusted track record. Dormancy followed by a minor patch is consistent with legitimate low-frequency maintenance of a mature library. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; a core dependency of this integration package. Not a risk. | ai | |
| dependencies | unvetted-dep:prosemirror-model | AI (dependencies): prosemirror-model is the core ProseMirror data model package by the same author; a fundamental dependency of this package. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): @types/markdown-it is declared as a dependency for TypeScript type distribution purposes; not a true phantom dependency risk. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.13.5 | 3 / 3 | |
| 1.13.4 | 3 / 3 | |
| 1.13.3 | 3 / 3 | |
| 1.13.2 | 3 / 3 | |
| 1.13.1 | 3 / 3 | |
| 1.13.0 | 2 / 4 | |
| 1.12.0 | 2 / 4 | |
| 1.11.2 | 2 / 4 | |
| 1.11.1 | 2 / 4 | |
| 1.11.0 | 2 / 4 | |
| 1.10.1 | 2 / 3 | |
| 1.10.0 | 2 / 3 | |
| 1.9.4 | 2 / 3 | |
| 1.9.3 | 2 / 3 | |
| 1.9.2 | 2 / 3 | |
| 1.9.1 | 2 / 3 | |
| 1.9.0 | 2 / 3 | |
| 1.8.0 | 2 / 7 | |
| 1.7.1 | 2 / 7 | |
| 1.7.0 | 2 / 7 | |
| 1.6.2 | 2 / 7 | |
| 1.6.1 | 2 / 7 | |
| 1.6.0 | 2 / 7 | |
| 1.5.2 | 2 / 7 | |
| 1.5.1 | 2 / 7 | |
| 1.5.0 | 2 / 7 | |
| 1.4.5 | 2 / 7 | |
| 1.4.4 | 2 / 7 | |
| 1.4.3 | 2 / 7 | |
| 1.4.2 | 2 / 7 | |
| 1.4.1 | 2 / 7 | |
| 1.4.0 | 2 / 7 | |
| 1.3.2 | 2 / 7 | |
| 1.3.1 | 2 / 7 | |
| 1.3.0 | 2 / 7 | |
| 1.2.2 | 2 / 7 | |
| 1.2.1 | 2 / 7 | |
| 1.2.0 | 2 / 7 | |
| 1.1.1 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.4 | 2 / 8 | |
| 1.0.3 | 2 / 8 | |
| 1.0.2 | 2 / 8 | |
| 1.0.1 | 2 / 8 | |
| 1.0.0 | 2 / 7 |
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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.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.