@tarojs/plugin-http
Taro 小程序端支持使用 web 请求 的插件
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/bigmeow | AI (email-domain): Author field uses a GitHub profile URL as email, not a real domain; no hijack risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @tarojs/* packages at matching version, consistent with monorepo release pattern. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 0 / 4 | |
| 4.1.11 | 0 / 4 | |
| 4.1.10 | 0 / 4 | |
| 4.1.9 | 0 / 4 | |
| 4.1.8 | 0 / 4 | |
| 4.1.7 | 0 / 4 | |
| 4.1.6 | 0 / 4 | |
| 4.1.5 | 0 / 4 | |
| 4.1.4 | 0 / 4 | |
| 4.1.3 | 0 / 4 | |
| 4.1.2 | 0 / 4 | |
| 4.1.1 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.13 | 0 / 4 | |
| 3.6.40 | 3 / 11 | |
| 3.6.39 | 3 / 11 |
v4.2.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingsMaintainer email 'https://github.com/bigmeow' uses domain 'https://github.com/bigmeow' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.39
2 findingsMaintainer email 'https://github.com/bigmeow' uses domain 'https://github.com/bigmeow' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.