@git.zone/tsbundle
a multi-bundler tool supporting esbuild, rolldown, and rspack for painless bundling of web projects
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist_ts/mod_custom/index.js | AI (source-diff): Long lines are from compiled TS with inline strings, not obfuscation; code is fully readable in sample. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_output/index.js | AI (source-diff): Long lines are from compiled TS with inline strings, not obfuscation; code is fully readable in sample. | ai | |
| source-diff | obfuscated-file:dist_ts/mod_init/index.js | AI (source-diff): Long lines are from compiled TS with inline strings, not obfuscation; code is fully readable in sample. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 28 approved packages in the same ecosystem; dormancy likely reflects development cadence, not takeover. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread used to pass environment to child thread in a build tool — standard subprocess pattern, not exfiltration. | ai | |
| phantom-deps | phantom-dep:@types/html-minifier | AI (phantom-deps): Type-only package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartdelay | AI (phantom-deps): May be used transitively or via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a build-time dep used via config; phantom detection is a false positive for this build tool. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 17 / 4 | |
| 2.8.2 | 17 / 4 | |
| 2.8.1 | 17 / 4 | |
| 2.6.3 | 15 / 4 | |
| 2.6.2 | 15 / 4 | |
| 2.6.1 | 15 / 4 | |
| 2.6.0 | 15 / 4 | |
| 2.5.2 | 15 / 5 | |
| 2.2.7 | 13 / 5 |
v2.10.1
3 findingsSpreading entire process.env into an object — may capture all secrets 26 | }; 27 | const threadsimple = new plugins.smartspawn.ThreadSimple(plugins.path.join(plugins.smartpath.get.dirnameFromImpo > 28 | env: { 29 | ...process.env, 30 | transportOptions: JSON.stringify(transportOptions),
Spreading entire process.env into an object — may capture all secrets 38 | [], 39 | { > 40 | env: { 41 | ...process.env, 42 | transportOptions: JSON.stringify(transportOptions),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.8.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.