react-native-drawer-layout
Drawer component for 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transfer from original author to react-navigation core maintainer satya164, a highly trusted publisher with 1332 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all known react-navigation team members; package was adopted into the official monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original maintainers removed as part of planned transfer to react-navigation team. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump with monorepo migration; new files are expected TS source + build outputs. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from monorepo restructuring with builder-bob outputs (CJS, ESM, types); expected for major version. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 2 / 10 | |
| 4.2.3 | 2 / 10 | |
| 4.2.2 | 2 / 10 | |
| 4.2.1 | 2 / 10 | |
| 4.2.0 | 2 / 10 | |
| 4.1.13 | 1 / 5 | |
| 4.1.12 | 1 / 5 | |
| 4.1.11 | 1 / 5 | |
| 4.1.10 | 1 / 5 | |
| 4.1.9 | 1 / 5 | |
| 4.1.8 | 1 / 5 | |
| 4.1.7 | 1 / 5 | |
| 4.1.6 | 1 / 5 | |
| 4.1.5 | 1 / 5 | |
| 4.1.4 | 1 / 5 | |
| 4.1.3 | 1 / 5 | |
| 4.1.2 | 1 / 5 | |
| 4.1.1 | 1 / 5 | |
| 4.1.0 | 1 / 5 | |
| 4.0.4 | 1 / 5 | |
| 4.0.3 | 1 / 5 | |
| 4.0.2 | 1 / 5 | |
| 4.0.1 | 1 / 5 | |
| 4.0.0 | 1 / 5 | |
| 3.3.2 | 1 / 5 | |
| 3.3.1 | 1 / 5 | |
| 3.3.0 | 1 / 5 | |
| 3.2.2 | 1 / 5 | |
| 3.2.1 | 1 / 5 | |
| 3.2.0 | 1 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.0.0 | 0 / 9 | |
| 1.3.2 | 1 / 7 | |
| 1.3.1 | 1 / 7 | |
| 1.3.0 | 1 / 17 | |
| 1.2.0 | 1 / 17 | |
| 1.1.6 | 1 / 17 | |
| 1.1.5 | 1 / 17 | |
| 1.1.4 | 2 / 15 | |
| 1.1.3 | 2 / 15 | |
| 1.1.2 | 2 / 15 | |
| 1.1.1 | 2 / 12 | |
| 1.1.0 | 2 / 12 | |
| 1.0.0 | 2 / 11 | |
| 0.5.1 | 2 / 11 | |
| 0.5.0 | 2 / 11 | |
| 0.4.2 | 2 / 11 | |
| 0.4.0 | 2 / 11 | |
| 0.3.6 | 2 / 11 | |
| 0.3.5 | 2 / 11 |
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.1
2 findingsThis version was published by a different npm account than previous versions on 2023-06-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-01-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.