@transifex/api
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @transifex/api is a legitimate scoped package; Levenshtein match against 'hapi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @transifex/api is a legitimate scoped package; Levenshtein match against 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @transifex/api is a legitimate scoped package; Levenshtein match against 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @transifex/api is a legitimate scoped package; Levenshtein match against 'ajv' is a false positive. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package. | ai |
v7.1.6
2 findingsPackage name '@transifex/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
2 findingsPackage name '@transifex/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
2 findingsPackage name '@transifex/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.