← Home

@widergy/mobile-ui

npm Repository Homepage
21
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

fiozzolisgulinogmlipinaalcurvelowidergy.npmsanticammguidodinatale

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 21 of 21)

Version Deps Published
2.22.1 25 / 46
2.22.0 25 / 46
2.21.0 26 / 44
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
1.52.0 17 / 33

v2.22.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.22.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.52.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.