@okta/okta-react-native
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jscodeshift | AI (phantom-deps): jscodeshift is used as a codemod/build tool dependency, not directly imported in runtime code; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-async-to-generator | AI (phantom-deps): Babel plugin loaded by convention via babel config, not directly imported; stable FP for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.18.1 | 6 / 23 | |
| 2.18.0 | 6 / 23 | |
| 2.17.2 | 5 / 23 | |
| 2.17.1 | 5 / 23 | |
| 2.17.0 | 5 / 23 | |
| 2.16.0 | 5 / 23 | |
| 2.15.0 | 6 / 23 | |
| 2.14.0 | 6 / 23 | |
| 2.13.0 | 6 / 23 |
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.