@brightlayer-ui/react-native-vector-icons
Brightlayer UI vector icons for use in React Native projects, based on react-native-vector-icons
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-native-vector-icons/common | AI (dependencies): This package is a direct wrapper around react-native-vector-icons; the common dep is the expected upstream dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established Eaton/Brightlayer UI package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 1 / 10 | |
| 3.2.1 | 1 / 10 | |
| 3.2.0 | 1 / 10 | |
| 3.1.0 | 1 / 10 | |
| 3.0.0 | 1 / 10 |
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.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.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.