@widergy/utilitygo-smart-bill-mobile MIT 10 versions

@widergy/utilitygo-smart-bill-mobile

npm

UtilityGO SmartBill Mobile

10

Versions

MIT

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fiozzolisgulinogmlipinaalcurvelowidergy.npmsanticammguidodinatale

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:core-js	AI (phantom-deps): core-js is a known implicit polyfill runtime dep; not directly imported by design.	ai	2026/04/29
phantom-deps	phantom-dep:react-native-pager-view	AI (phantom-deps): Platform-specific binary package; not directly imported by JS source.	ai	2026/04/29
phantom-deps	phantom-dep:react-native-image-picker	AI (phantom-deps): Platform-specific binary package; not directly imported by JS source.	ai	2026/04/29
phantom-deps	phantom-dep:react-native-vector-icons	AI (phantom-deps): Platform-specific binary package; not directly imported by JS source.	ai	2026/04/29
phantom-deps	phantom-dep:@react-native-community/art	AI (phantom-deps): Platform-specific binary package; not directly imported by JS source.	ai	2026/04/29
phantom-deps	phantom-dep:react-native-svg-transformer	AI (phantom-deps): Build-time transformer; not directly imported by JS source.	ai	2026/04/29

Versions (showing 10 of 10)

Version	Deps	Published
3.13.2	17 / 48	2026-05-21
3.13.0	17 / 48	2026-04-27
3.12.2	17 / 48	2026-04-14
3.8.0	17 / 36	2026-02-02
3.7.0	17 / 36	2026-01-27
3.6.1	17 / 36	2026-01-14
3.5.1	17 / 36	2025-12-10
3.5.0	17 / 36	2025-12-03
3.4.0	17 / 36	2025-11-07
3.3.0	17 / 36	2025-11-05

v3.13.2

1 finding

LOW No provenance attestation provenance

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

v3.12.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.8.0

1 finding

LOW No provenance attestation provenance

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

v3.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.