@types/uglify-js
TypeScript definitions for uglify-js
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/tkrotoff | AI (email-domain): The 'email' field contains a GitHub profile URL, not an email address. The analyzer is misidentifying a URL as an email domain — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/source-map | AI (phantom-deps): @types packages use type-level dependencies that aren't directly imported via require(). This is expected behavior for DefinitelyTyped packages. | ai | |
| source-diff | net-exec-file:uglify-js/index.d.ts | AI (source-diff): This is a TypeScript .d.ts type definition file. The 'network call' is a module import statement and the 'code execution' is type definitions for UglifyJS APIs. No actual executable code or network activity is present. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.17.5 | 1 / 0 | |
| 3.17.4 | 1 / 0 | |
| 3.17.3 | 1 / 0 | |
| 3.17.2 | 1 / 0 | |
| 3.17.1 | 1 / 0 | |
| 3.17.0 | 1 / 0 | |
| 3.16.0 | 1 / 0 | |
| 3.13.3 | 1 / 0 | |
| 3.13.2 | 1 / 0 | |
| 3.13.1 | 1 / 0 | |
| 3.13.0 | 1 / 0 | |
| 3.12.0 | 1 / 0 | |
| 3.11.1 | 1 / 0 | |
| 3.11.0 | 1 / 0 | |
| 3.9.3 | 1 / 0 | |
| 3.9.2 | 1 / 0 | |
| 3.9.1 | 1 / 0 | |
| 3.9.0 | 1 / 0 | |
| 3.0.5 | 1 / 0 | |
| 3.0.4 | 1 / 0 | |
| 3.0.3 | 1 / 0 | |
| 3.0.2 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 0 | |
| 2.6.37 | 1 / 0 | |
| 2.6.36 | 1 / 0 | |
| 2.6.35 | 1 / 0 | |
| 2.6.34 | 1 / 0 | |
| 2.6.33 | 1 / 0 | |
| 2.6.32 | 1 / 0 | |
| 2.6.31 | 1 / 0 | |
| 2.6.30 | 1 / 0 | |
| 2.6.29 | 1 / 0 | |
| 2.6.28 | 1 / 0 | |
| 2.0.27 | 1 / 0 |
v3.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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.6.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
2 findingsMaintainer email 'https://github.com/tkrotoff' uses domain 'https://github.com/tkrotoff' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.