@react-navigation/material-top-tabs
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established react-navigation monorepo package; lack of provenance is consistent across all versions. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 7.6.13 | 3 / 12 | |
| 7.6.12 | 3 / 12 | |
| 7.6.11 | 3 / 12 | |
| 7.6.10 | 3 / 12 | |
| 7.6.9 | 3 / 12 | |
| 7.6.8 | 3 / 12 | |
| 7.6.7 | 3 / 12 | |
| 7.6.6 | 3 / 12 | |
| 7.6.5 | 3 / 12 | |
| 7.6.4 | 3 / 12 | |
| 7.6.3 | 3 / 12 | |
| 7.6.2 | 3 / 12 | |
| 7.6.1 | 3 / 12 | |
| 7.6.0 | 3 / 12 | |
| 7.5.2 | 3 / 12 | |
| 7.5.1 | 3 / 12 | |
| 7.5.0 | 3 / 12 | |
| 7.4.28 | 3 / 12 | |
| 7.4.27 | 3 / 12 | |
| 7.4.26 | 3 / 12 | |
| 7.4.25 | 3 / 12 | |
| 7.4.24 | 3 / 12 | |
| 7.4.23 | 3 / 12 | |
| 7.4.22 | 3 / 12 | |
| 7.4.21 | 3 / 12 | |
| 7.4.20 | 3 / 12 | |
| 7.4.19 | 3 / 12 | |
| 7.4.18 | 3 / 12 | |
| 7.4.17 | 3 / 12 | |
| 7.4.16 | 3 / 12 | |
| 7.4.15 | 3 / 12 | |
| 7.4.14 | 3 / 12 | |
| 7.4.13 | 3 / 12 | |
| 7.4.12 | 3 / 12 | |
| 7.4.11 | 3 / 12 | |
| 7.4.10 | 3 / 13 | |
| 7.4.9 | 3 / 13 | |
| 7.4.8 | 3 / 13 | |
| 7.4.7 | 3 / 13 | |
| 7.4.6 | 3 / 13 | |
| 7.4.5 | 3 / 13 | |
| 7.4.4 | 3 / 13 | |
| 7.4.3 | 3 / 13 | |
| 7.4.2 | 3 / 13 | |
| 7.4.1 | 3 / 13 | |
| 7.4.0 | 3 / 13 | |
| 7.3.9 | 3 / 13 | |
| 7.3.8 | 3 / 12 | |
| 7.3.7 | 3 / 12 | |
| 7.3.6 | 3 / 12 | |
| 7.3.5 | 3 / 12 | |
| 7.3.4 | 3 / 12 | |
| 7.3.3 | 3 / 12 | |
| 7.3.2 | 3 / 12 | |
| 7.3.1 | 3 / 12 | |
| 7.3.0 | 3 / 12 | |
| 7.2.17 | 3 / 12 | |
| 7.2.16 | 3 / 12 | |
| 7.2.15 | 3 / 12 | |
| 7.2.14 | 3 / 12 | |
| 7.2.13 | 3 / 12 | |
| 7.2.12 | 3 / 12 | |
| 7.2.11 | 3 / 12 | |
| 7.2.10 | 3 / 12 | |
| 7.2.9 | 3 / 10 | |
| 7.2.8 | 3 / 10 | |
| 7.2.7 | 3 / 10 | |
| 7.2.6 | 3 / 10 | |
| 7.2.5 | 3 / 10 | |
| 7.2.4 | 3 / 10 | |
| 7.2.3 | 3 / 10 | |
| 7.2.2 | 3 / 10 | |
| 7.2.1 | 3 / 10 | |
| 7.2.0 | 3 / 10 | |
| 7.1.1 | 3 / 10 | |
| 7.1.0 | 3 / 10 | |
| 7.0.18 | 3 / 10 | |
| 7.0.17 | 3 / 10 | |
| 7.0.16 | 3 / 10 | |
| 7.0.15 | 3 / 10 | |
| 7.0.14 | 3 / 10 | |
| 7.0.13 | 3 / 10 | |
| 7.0.12 | 3 / 10 | |
| 7.0.11 | 3 / 10 | |
| 7.0.10 | 3 / 10 | |
| 7.0.9 | 3 / 10 | |
| 7.0.8 | 3 / 10 | |
| 7.0.7 | 3 / 10 | |
| 7.0.6 | 3 / 10 | |
| 7.0.5 | 3 / 10 | |
| 7.0.4 | 3 / 10 | |
| 7.0.3 | 3 / 10 | |
| 7.0.2 | 3 / 10 | |
| 7.0.1 | 3 / 10 | |
| 7.0.0 | 3 / 10 |
v7.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.