typescript-json-schema
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is core to this package's functionality — it loads user-specified TypeScript/JS files to generate JSON schemas. This is expected and documented behavior. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; used as a type dependency re-export pattern, not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): Framework-scoped type package; used as a type dependency re-export pattern, not a real phantom dep risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.67.4 | 9 / 9 | |
| 0.67.3 | 9 / 9 | |
| 0.67.2 | 9 / 9 | |
| 0.67.0 | 8 / 10 | |
| 0.66.0 | 8 / 10 |
v0.67.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.