prismic-ts-codegen
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.30 | 9 / 11 | |
| 0.1.29 | 9 / 11 | |
| 0.1.28 | 9 / 21 | |
| 0.1.27 | 9 / 21 | |
| 0.1.26 | 9 / 21 | |
| 0.1.25 | 9 / 21 | |
| 0.1.24 | 9 / 21 | |
| 0.1.23 | 9 / 21 | |
| 0.1.22 | 9 / 21 |
v0.1.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
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 (levimykel) than the most recent previously approved version (angeloashmore) on 2025-06-25, but levimykel 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.26
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 (angeloashmore) than the most recent previously approved version (lihbr) on 2025-04-25, but angeloashmore 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.25
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 (dani-mp) than the most recent previously approved version (lihbr) on 2025-02-11, but dani-mp 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.24
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 (lihbr) than the most recent previously approved version (dani-mp) on 2025-01-20, but lihbr 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.23
2 findingsThis version was published by a different npm account (dani-mp) than the most recent previously approved version (lihbr) on 2024-12-05. It has since remained available on npm for 593 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.