@fingerprintjs/fingerprintjs-pro-react-native
Official React Native client for Fingerprint. Best identification solution for React Native.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.14.0 | 0 / 23 | |
| 3.13.0 | 0 / 23 | |
| 3.12.0 | 0 / 23 | |
| 3.11.0 | 0 / 23 | |
| 3.10.0 | 0 / 23 | |
| 3.9.0 | 0 / 23 | |
| 3.8.0 | 0 / 23 | |
| 3.7.0 | 0 / 36 | |
| 3.6.0 | 0 / 36 | |
| 3.5.0 | 0 / 38 | |
| 3.4.1 | 0 / 38 | |
| 3.4.0 | 0 / 38 |
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.