tshy
TypeScript HYbridizer - Hybrid (CommonJS/ESM) TypeScript node package builder
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/bin-min.mjs | AI (source-diff): bin-min.mjs is an esbuild-bundled CLI entry point (chalk/ansi code visible in sample). Standard pattern for CLI tools; esbuild is in devDeps. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from bundling CLI binary via esbuild. Consistent with bin-min.mjs addition. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 13 / 7 | |
| 4.1.1 | 13 / 7 | |
| 4.1.0 | 13 / 7 | |
| 4.0.0 | 13 / 7 | |
| 3.3.2 | 13 / 5 | |
| 3.3.1 | 13 / 5 | |
| 3.3.0 | 13 / 5 | |
| 3.2.1 | 12 / 5 | |
| 3.2.0 | 12 / 5 | |
| 3.1.3 | 11 / 5 | |
| 3.1.2 | 11 / 5 | |
| 3.1.1 | 11 / 4 | |
| 3.1.0 | 11 / 4 | |
| 3.0.3 | 11 / 4 | |
| 3.0.2 | 11 / 4 | |
| 3.0.1 | 11 / 4 | |
| 3.0.0 | 11 / 4 | |
| 2.0.1 | 11 / 4 | |
| 2.0.0 | 11 / 4 | |
| 1.18.0 | 11 / 4 | |
| 1.17.0 | 11 / 4 | |
| 1.16.2 | 11 / 4 | |
| 1.16.1 | 11 / 4 | |
| 1.16.0 | 11 / 4 | |
| 1.15.1 | 11 / 4 | |
| 1.15.0 | 11 / 4 | |
| 1.14.1 | 11 / 4 | |
| 1.14.0 | 11 / 4 | |
| 1.13.1 | 10 / 4 | |
| 1.13.0 | 10 / 4 | |
| 1.12.0 | 10 / 4 | |
| 1.11.1 | 10 / 4 | |
| 1.11.0 | 9 / 4 | |
| 1.10.0 | 9 / 4 | |
| 1.9.0 | 9 / 4 | |
| 1.8.2 | 9 / 4 | |
| 1.8.1 | 9 / 4 | |
| 1.8.0 | 9 / 4 | |
| 1.7.0 | 9 / 4 | |
| 1.6.0 | 8 / 4 | |
| 1.5.0 | 8 / 4 | |
| 1.4.0 | 8 / 4 | |
| 1.3.0 | 8 / 4 | |
| 1.2.2 | 8 / 4 | |
| 1.2.1 | 8 / 4 | |
| 1.2.0 | 8 / 4 | |
| 1.1.1 | 8 / 4 | |
| 1.1.0 | 7 / 4 | |
| 1.0.0 | 6 / 4 |
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.