@git.zone/tsdocker
A comprehensive Docker build tool for TypeScript projects with multi-arch support, multi-registry push, and CI-safe session isolation.
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_ts/tsdocker.docker.js | AI (source-diff): Readable compiled TS output; long lines from build bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/classes.dockerregistry.js | AI (source-diff): Readable compiled TS output; long lines from build bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/classes.tsdockermanager.js | AI (source-diff): Readable compiled TS output; long lines from build bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/tsdocker.cli.js | AI (source-diff): Readable compiled TS output; long lines from build bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/classes.dockerfile.js | AI (source-diff): Readable compiled TS output; long lines from build bundler, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartanalytics | AI (phantom-deps): Publisher's own dep; declared in config for analytics opt-in, not a phantom risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding Docker registry auth tokens from config.json — standard Docker credential handling, not obfuscated payload. | ai | |
| semgrep | semgrep:ssh-key-access | AI (semgrep): Fires on an interface field declaration for SSH key path in a Docker multi-arch build tool; not credential theft. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.2.5 | 10 / 4 | |
| 1.7.0 | 14 / 4 | |
| 1.4.2 | 14 / 4 | |
| 1.2.43 | 13 / 4 |
v2.2.5
2 findingsAccessing SSH keys — strong indicator of credential theft 105 | host: string; // e.g., "[email protected]" 106 | platform: string; // e.g., "linux/arm64" > 107 | sshKeyPath?: string; // e.g., "~/.ssh/id_ed25519" 108 | } 109 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
6 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.
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.
v1.4.2
6 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.
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.
v1.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.