@tarojs/api
Taro common 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @tarojs/api is a long-established Taro framework package (2237 days, 840 versions). The Levenshtein match against 'hapi' is a false positive on the scoped package name. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @tarojs/api is a legitimate Taro monorepo sub-package; no relation to 'pg'. False positive from scoped name comparison. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @tarojs/api is a legitimate Taro monorepo sub-package; no relation to 'joi'. False positive from scoped name comparison. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @tarojs/api is a legitimate Taro monorepo sub-package; no relation to 'ajv'. False positive from scoped name comparison. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 0 / 3 | |
| 4.1.11 | 0 / 3 | |
| 4.1.10 | 0 / 3 | |
| 4.1.9 | 0 / 3 | |
| 4.1.8 | 0 / 3 | |
| 4.1.7 | 0 / 3 | |
| 4.1.6 | 0 / 3 | |
| 4.1.5 | 0 / 3 | |
| 4.1.4 | 0 / 3 | |
| 4.1.3 | 0 / 3 | |
| 4.1.2 | 0 / 3 | |
| 4.1.1 | 0 / 3 | |
| 4.1.0 | 0 / 3 | |
| 4.0.13 | 0 / 3 | |
| 3.6.40 | 3 / 13 | |
| 3.6.39 | 3 / 13 |
v4.2.0
2 findingsPackage name '@tarojs/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.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.40
2 findingsPackage name '@tarojs/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.
v3.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.