@widergy/mobile-ui
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): dayjs is a well-established, widely-used date library with no malicious history; addition is benign. | ai | |
| provenance | no-provenance | AI (provenance): Established internal UI library; provenance not configured but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a well-known implicit polyfill dependency; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:react-native-worklets | AI (phantom-deps): Platform-specific binary package; phantom-dep heuristic is a known false positive for native modules. | ai | |
| phantom-deps | phantom-dep:@react-navigation/native | AI (phantom-deps): Referenced in config files; phantom-dep false positive for navigation peer/config usage. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.17.1 | 23 / 44 | |
| 2.15.0 | 22 / 44 | |
| 2.14.0 | 22 / 44 | |
| 2.9.6 | 22 / 44 | |
| 2.9.5 | 22 / 44 | |
| 2.9.4 | 22 / 44 | |
| 2.9.3 | 22 / 44 | |
| 2.9.1 | 22 / 44 | |
| 2.5.0 | 21 / 33 | |
| 2.4.0 | 21 / 33 | |
| 2.3.4 | 21 / 33 | |
| 2.3.1 | 21 / 33 | |
| 2.3.0 | 21 / 33 | |
| 2.1.4 | 21 / 33 | |
| 2.1.2 | 21 / 33 | |
| 2.1.1 | 21 / 33 | |
| 2.0.0 | 21 / 33 |
v2.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.