@medusajs/http-types-generator
Generate and validate HTTP TypeScript types
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA provenance; consistent with medusajs monorepo CI publishing migration. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.15.5 | 6 / 2 | |
| 2.15.3 | 6 / 2 | |
| 2.15.2 | 6 / 2 | |
| 2.15.1 | 6 / 2 | |
| 2.15.0 | 6 / 2 | |
| 2.14.2 | 6 / 2 | |
| 2.14.1 | 6 / 2 | |
| 2.14.0 | 6 / 2 | |
| 2.13.6 | 6 / 2 |
v2.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.