@react-navigation/drawer
Integration for the drawer component from react-native-drawer-layout
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
Keywords
Versions (showing 100 of 204)
| Version | Deps | Published |
|---|---|---|
| 6.6.6 | 3 / 13 | |
| 6.6.5 | 3 / 13 | |
| 6.6.4 | 3 / 13 | |
| 6.6.3 | 3 / 13 | |
| 6.6.2 | 3 / 13 | |
| 6.6.1 | 3 / 13 | |
| 6.6.0 | 3 / 13 | |
| 6.5.8 | 3 / 13 | |
| 6.5.7 | 3 / 13 | |
| 6.5.6 | 3 / 13 | |
| 6.5.5 | 3 / 13 | |
| 6.5.4 | 3 / 13 | |
| 6.5.3 | 3 / 13 | |
| 6.5.1 | 3 / 13 | |
| 6.5.0 | 3 / 13 | |
| 6.4.4 | 3 / 13 | |
| 6.4.3 | 3 / 13 | |
| 6.4.2 | 3 / 13 | |
| 6.4.1 | 3 / 13 | |
| 6.4.0 | 3 / 13 | |
| 6.3.3 | 3 / 13 | |
| 6.3.2 | 3 / 13 | |
| 6.3.1 | 3 / 13 | |
| 6.3.0 | 3 / 13 | |
| 6.2.0 | 3 / 13 | |
| 6.1.8 | 3 / 13 | |
| 6.1.7 | 3 / 13 | |
| 6.1.6 | 3 / 13 | |
| 6.1.5 | 3 / 13 | |
| 6.1.4 | 3 / 13 | |
| 6.1.3 | 3 / 13 | |
| 6.1.2 | 3 / 13 | |
| 6.1.1 | 3 / 13 | |
| 6.1.0 | 3 / 13 | |
| 6.0.1 | 3 / 13 | |
| 6.0.0 | 3 / 13 | |
| 5.12.9 | 2 / 13 | |
| 5.12.8 | 2 / 13 | |
| 5.12.7 | 2 / 13 | |
| 5.12.5 | 2 / 13 | |
| 5.12.4 | 2 / 13 | |
| 5.12.3 | 2 / 13 | |
| 5.12.2 | 2 / 13 | |
| 5.12.1 | 2 / 13 | |
| 5.12.0 | 2 / 13 | |
| 5.11.5 | 2 / 13 | |
| 5.11.4 | 2 / 13 | |
| 5.11.3 | 2 / 13 | |
| 5.11.2 | 2 / 13 | |
| 5.11.1 | 2 / 13 | |
| 5.11.0 | 2 / 13 | |
| 5.10.7 | 2 / 13 | |
| 5.10.6 | 2 / 13 | |
| 5.10.5 | 2 / 13 | |
| 5.10.4 | 2 / 13 | |
| 5.10.3 | 2 / 13 | |
| 5.10.2 | 2 / 13 | |
| 5.10.1 | 2 / 13 | |
| 5.10.0 | 2 / 13 | |
| 5.9.3 | 2 / 13 | |
| 5.9.2 | 2 / 13 | |
| 5.9.1 | 2 / 13 | |
| 5.9.0 | 2 / 13 | |
| 5.8.7 | 2 / 13 | |
| 5.8.6 | 2 / 13 | |
| 5.8.5 | 2 / 13 | |
| 5.8.4 | 2 / 12 | |
| 5.8.3 | 2 / 12 | |
| 5.8.2 | 2 / 12 | |
| 5.8.1 | 2 / 12 | |
| 5.8.0 | 2 / 12 | |
| 5.7.7 | 2 / 12 | |
| 5.7.6 | 2 / 12 | |
| 5.7.5 | 2 / 12 | |
| 5.7.4 | 2 / 12 | |
| 5.7.3 | 2 / 12 | |
| 5.7.2 | 2 / 12 | |
| 5.7.1 | 2 / 12 | |
| 5.7.0 | 2 / 12 | |
| 5.6.4 | 2 / 12 | |
| 5.6.3 | 2 / 12 | |
| 5.6.2 | 2 / 12 | |
| 5.6.1 | 2 / 12 | |
| 5.6.0 | 2 / 12 | |
| 5.5.1 | 2 / 12 | |
| 5.5.0 | 2 / 12 | |
| 5.4.1 | 2 / 12 | |
| 5.4.0 | 2 / 12 | |
| 5.3.4 | 2 / 12 | |
| 5.3.3 | 2 / 12 | |
| 5.3.2 | 2 / 12 | |
| 5.3.1 | 2 / 12 | |
| 5.3.0 | 2 / 12 | |
| 5.2.0 | 2 / 12 | |
| 5.1.1 | 2 / 12 | |
| 5.1.0 | 2 / 12 | |
| 5.0.7 | 2 / 12 | |
| 5.0.6 | 2 / 12 | |
| 5.0.5 | 2 / 12 | |
| 5.0.4 | 2 / 12 |
v6.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.