@diplodoc/folding-headings-extension
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 0 / 8 | |
| 0.2.3 | 0 / 8 | |
| 0.2.2 | 0 / 8 | |
| 0.2.1 | 0 / 9 | |
| 0.2.0 | 0 / 9 | |
| 0.1.3 | 0 / 8 | |
| 0.1.2 | 0 / 13 | |
| 0.1.1 | 0 / 13 | |
| 0.1.0 | 0 / 13 |
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robot-dataui-npm) than the most recent previously approved version (makhnatkin) on 2024-12-11, but robot-dataui-npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robot-dataui-npm) than the most recent previously approved version (makhnatkin) on 2024-12-11, but robot-dataui-npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.