The package is easy to inspect, with a clear README, stable versioning, and only one runtime dependency. Its four-file project lacks tests and security scanning, limiting confidence for a routing library.
62%
Total Score
50
100
83
75
Only one registry account has publish access. With a user-owned repository and no organizational backing shown, the project has limited apparent maintainer redundancy.
The package and repository each contain only four files: a README, Composer metadata, and one source file. This is easy to inspect but leaves little visible project structure for validating a routing library.
The registry namespace and repository are owned by the same individual account, confirming direct ownership but not providing organizational backing or additional maintenance capacity.
The package has existed for about 690 days but has only three releases, with two releases in the last year and a median interval of about 241 days. This suggests modest maintenance rather than an actively evolving project.
The repository recorded zero commits and zero active maintainers in the last three months. Although the latest release was pushed in March 2026, the lack of recent activity weakens confidence in ongoing maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bramus/router Version ^1.6 | — | — |
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.