Modern and scalable routing for React applications
87%
Total Score
healthy
Active organization-backed project with frequent releases and provenance; package identification and security-policy gaps trim confidence.
The repository name does not match the package name and its README does not mention this package, so the package-to-repository relationship is less transparent; the organization and active monorepo context partly compensate.
The repository has no published security policy, leaving vulnerability-reporting expectations and response procedures less transparent.
All nine workflows were analyzed with no high- or medium-severity findings, no untrusted checkouts, no script injection, and all 33 action references pinned. Three high-confidence low-severity adhoc-package findings and three workflows with top-level write permissions are modest hygiene concerns.
| Dependency | Last Release | Score |
|---|---|---|
diff Version ^9.0.0 | — | — |
ansis Version ^4.3.1 | — | — |
pathe Version ^2.0.3 | — | — |
tinyglobby Version ^0.2.17 | — | — |
@babel/types Version ^7.29.8 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.