@icanbwell/native-plugins
@icanbwell/native-plugins. repo version: 17.27.3
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@icanbwell/types | AI (dependencies): Internal scoped dependency from the same icanbwell org; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@icanbwell/react-native-webview-invoke | AI (dependencies): Internal scoped dependency from the same icanbwell org; expected pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Org package with long publish history; lack of Sigstore provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.13.2 | 3 / 0 | |
| 7.13.1 | 3 / 0 | |
| 7.13.0 | 3 / 0 | |
| 7.12.5 | 3 / 0 | |
| 7.12.4 | 3 / 0 | |
| 7.12.3 | 3 / 0 | |
| 7.10.1 | 3 / 0 | |
| 7.9.0 | 3 / 0 | |
| 7.8.1 | 3 / 0 | |
| 7.8.0 | 3 / 0 | |
| 7.7.1 | 3 / 0 | |
| 7.7.0 | 3 / 0 | |
| 7.6.0 | 3 / 0 | |
| 6.3.1 | 3 / 0 | |
| 6.3.0 | 3 / 0 |
v7.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.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.
v7.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.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.
v7.6.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.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.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.