antd-mobile
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:antd-mobile-v5-count | AI (phantom-deps): antd-mobile-v5-count is a first-party companion package referenced in config files; not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Ant Design ecosystem package with verified GitHub repo; lack of Sigstore provenance is not a security risk here. | ai | |
| dependencies | unvetted-dep:antd-mobile-icons | AI (dependencies): antd-mobile-icons is a first-party companion package from the Ant Design org; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:antd-mobile-v5-count | AI (dependencies): antd-mobile-v5-count is a first-party companion package from the Ant Design org; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:staged-components | AI (dependencies): staged-components is a legitimate React utility library with no known security issues; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:nano-memoize | AI (dependencies): nano-memoize is a well-known memoization utility with no known security issues; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a popular, established React animation library; stable dependency for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.42.3 | 20 / 0 | |
| 5.42.2 | 20 / 0 | |
| 5.42.1 | 20 / 0 | |
| 5.42.0 | 20 / 0 | |
| 5.41.1 | 20 / 0 | |
| 5.41.0 | 20 / 0 | |
| 5.40.0 | 20 / 0 |
v5.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.