prosemirror-flat-list
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 8 / 18 | |
| 0.7.0 | 8 / 18 | |
| 0.6.0 | 7 / 18 | |
| 0.5.8 | 7 / 26 | |
| 0.5.7 | 7 / 26 | |
| 0.5.6 | 7 / 29 | |
| 0.5.5 | 7 / 29 | |
| 0.5.4 | 7 / 30 | |
| 0.5.3 | 7 / 30 | |
| 0.5.2 | 7 / 30 | |
| 0.5.1 | 7 / 30 |
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.