tt-uploader
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Standard minified UMD bundle output, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher change is old and stable, not a fresh compromise signal. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Declared in dependencies; phantom-dep is a heuristic false positive here. | ai | |
| phantom-deps | phantom-dep:jsrsasign | AI (phantom-deps): Declared in dependencies; phantom-dep is a heuristic false positive here. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Declared in dependencies; phantom-dep is a heuristic false positive here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 3 / 0 | |
| 1.6.1 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.5 | 3 / 0 | |
| 1.5.4 | 3 / 0 | |
| 1.5.3 | 3 / 0 | |
| 1.5.2 | 3 / 0 | |
| 1.5.1 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.0 | 3 / 0 | |
| 1.3.9 | 3 / 0 | |
| 1.3.8 | 3 / 0 | |
| 1.3.7 | 3 / 0 | |
| 1.3.6 | 3 / 0 | |
| 1.3.5 | 3 / 0 | |
| 1.3.4 | 3 / 0 | |
| 1.3.3 | 3 / 0 | |
| 1.3.2 | 3 / 0 |
v1.5.3
2 findingsThis version was published by a different npm account (xuguoqing) than the most recent previously approved version (huangkaisheng.0x0) on 2025-10-10. It has since remained available on npm for 281 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
2 findingsThis version was published by a different npm account (xuguoqing) than the most recent previously approved version (huangkaisheng.0x0) on 2025-09-30. It has since remained available on npm for 291 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2025-05-09. It has since remained available on npm for 435 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2025-04-25. It has since remained available on npm for 449 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2025-04-09. It has since remained available on npm for 465 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2024-12-11. It has since remained available on npm for 584 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2024-09-25. It has since remained available on npm for 661 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (gillian97) on 2024-09-23. It has since remained available on npm for 663 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.