react-router-dom
Declarative routing for React web applications
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): react-router-dom is a canonical, widely-used React routing library by Remix Software. Spam co-maintainer association and short README are false positives for this well-established package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation was not standard practice at the time of this release; absence is expected for this package version and not a risk indicator. | ai |
Versions (showing 35 of 135)
| Version | Deps | Published |
|---|---|---|
| 6.4.3 | 2 / 2 | |
| 6.4.2 | 2 / 2 | |
| 6.4.1 | 2 / 2 | |
| 6.4.0 | 1 / 2 | |
| 6.3.0 | 2 / 0 | |
| 6.2.2 | 2 / 0 | |
| 6.2.1 | 2 / 0 | |
| 6.2.0 | 2 / 0 | |
| 6.1.1 | 2 / 0 | |
| 6.1.0 | 2 / 0 | |
| 6.0.2 | 2 / 0 | |
| 6.0.1 | 2 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.3.4 | 7 / 0 | |
| 5.3.3 | 7 / 0 | |
| 5.3.2 | 7 / 0 | |
| 5.3.1 | 7 / 0 | |
| 5.3.0 | 7 / 0 | |
| 5.2.1 | 7 / 0 | |
| 5.2.0 | 7 / 0 | |
| 5.1.2 | 7 / 0 | |
| 5.1.1 | 7 / 0 | |
| 5.1.0 | 7 / 0 | |
| 5.0.1 | 7 / 23 | |
| 5.0.0 | 7 / 24 | |
| 4.3.1 | 6 / 26 | |
| 4.3.0 | 5 / 27 | |
| 4.2.2 | 6 / 24 | |
| 4.2.1 | 6 / 24 | |
| 4.2.0 | 5 / 24 | |
| 4.1.2 | 4 / 28 | |
| 4.1.1 | 4 / 28 | |
| 4.1.0 | 4 / 28 | |
| 4.0.0 | 2 / 29 | |
| 0.0.0 | 0 / 0 |
v6.4.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.
v6.4.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.
v6.4.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.
v6.4.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.
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.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.