@icanbwell/types
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package with long history; lack of provenance attestation is consistent across all versions. | ai | |
| dependencies | unvetted-dep:apollo-link-rest | AI (dependencies): Known Apollo GraphQL REST link package; consistent with healthcare app types library. | ai | |
| dependencies | unvetted-dep:react-native-android-location-enabler | AI (dependencies): Standard React Native location utility; consistent with mobile types package. | ai | |
| dependencies | unvetted-dep:@validic-mobile/react-native-inform-core | AI (dependencies): Validic mobile health SDK; expected dependency for healthcare types package. | ai | |
| dependencies | unvetted-dep:@validic-mobile/react-native-inform-healthkit | AI (dependencies): Validic HealthKit SDK; expected dependency for healthcare types package. | ai | |
| dependencies | unvetted-dep:@validic-mobile/react-native-inform-healthconnect | AI (dependencies): Validic HealthConnect SDK; expected dependency for healthcare types package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 7.12.0 | 5 / 0 | |
| 7.10.1 | 5 / 0 | |
| 7.9.0 | 5 / 0 | |
| 7.8.0 | 2 / 0 | |
| 7.5.0 | 2 / 0 | |
| 7.3.1 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.2.0 | 2 / 0 | |
| 7.1.1 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.5.0 | 2 / 0 | |
| 6.4.1 | 2 / 0 | |
| 6.4.0 | 2 / 0 | |
| 6.3.1 | 2 / 0 | |
| 6.3.0 | 2 / 0 |
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.