@dynamic-labs/react-native-extension
This library was generated with [Nx](https://nx.dev).
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is a documented org-wide CI/CD migration pattern for @dynamic-labs packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-native-fs and @react-native-documents/picker are established RN libraries appropriate for a native extension package. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URLs are Dynamic Labs' own staging/prod domains (dynamic-preprod.xyz, dynamicauth.com); not C2/exfiltration. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/webview-messages | AI (phantom-deps): Same-org dependency; declared in package.json at matching version, likely re-exported rather than directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is consistent across all 521 versions of this org's packages; not indicative of spam or malice. | ai |
Versions (showing 68 of 268)
| Version | Deps | Published |
|---|---|---|
| 4.18.3 | 5 / 0 | |
| 4.18.2 | 5 / 0 | |
| 4.18.1 | 5 / 0 | |
| 4.18.0 | 5 / 0 | |
| 4.17.0 | 5 / 0 | |
| 4.16.0 | 5 / 0 | |
| 4.15.0 | 5 / 0 | |
| 4.14.0 | 5 / 0 | |
| 4.13.0 | 5 / 0 | |
| 4.12.4 | 5 / 0 | |
| 4.12.3 | 5 / 0 | |
| 4.12.2 | 5 / 0 | |
| 4.12.1 | 5 / 0 | |
| 4.12.0 | 5 / 0 | |
| 4.11.2 | 5 / 0 | |
| 4.11.1 | 5 / 0 | |
| 4.11.0 | 5 / 0 | |
| 4.10.4 | 5 / 0 | |
| 4.10.3 | 5 / 0 | |
| 4.10.2 | 5 / 0 | |
| 4.10.1 | 5 / 0 | |
| 4.10.0 | 5 / 0 | |
| 4.9.12 | 5 / 0 | |
| 4.9.11 | 5 / 0 | |
| 4.9.10 | 5 / 0 | |
| 4.9.9 | 5 / 0 | |
| 4.9.8 | 5 / 0 | |
| 4.9.7 | 5 / 0 | |
| 4.9.6 | 5 / 0 | |
| 4.9.5 | 5 / 0 | |
| 4.9.4 | 5 / 0 | |
| 4.9.3 | 5 / 0 | |
| 4.9.2 | 5 / 0 | |
| 4.9.1 | 5 / 0 | |
| 4.9.0 | 5 / 0 | |
| 4.8.6 | 5 / 0 | |
| 4.8.5 | 5 / 0 | |
| 4.8.4 | 5 / 0 | |
| 4.8.3 | 5 / 0 | |
| 4.8.2 | 5 / 0 | |
| 4.8.1 | 5 / 0 | |
| 4.8.0 | 5 / 0 | |
| 4.7.2 | 5 / 0 | |
| 4.7.1 | 5 / 0 | |
| 4.7.0 | 5 / 0 | |
| 4.6.3 | 5 / 0 | |
| 4.6.2 | 5 / 0 | |
| 4.6.1 | 5 / 0 | |
| 4.6.0 | 5 / 0 | |
| 4.5.3 | 5 / 0 | |
| 4.5.2 | 5 / 0 | |
| 4.5.1 | 5 / 0 | |
| 4.5.0 | 5 / 0 | |
| 4.4.4 | 5 / 0 | |
| 4.4.3 | 5 / 0 | |
| 4.4.2 | 5 / 0 | |
| 4.4.1 | 5 / 0 | |
| 4.4.0 | 5 / 0 | |
| 4.3.2 | 5 / 0 | |
| 4.3.1 | 5 / 0 | |
| 4.3.0 | 5 / 0 | |
| 4.2.3 | 5 / 0 | |
| 4.2.2 | 5 / 0 | |
| 4.2.1 | 5 / 0 | |
| 4.2.0 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 |
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.