The repository has no security policy or security-scanning tools, and its public footprint is minimal. MIT licensing, a clear package tree, and release notes for this version provide useful transparency.
53%
Total Score
50
100
75
50
The package has 89 releases over about two and a half years, but no releases in the last 12 months; the latest release was about 18 months ago. This sharply raises abandonment concern despite the earlier release cadence.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but current maintenance activity is absent.
The repository has zero stars and forks and only one watcher, providing little evidence of external adoption or review. Popularity is supporting evidence rather than a verdict, so this weighs modestly against the package.
Composer build tooling is present, which supports reproducible package management, but no security-scanning tools were detected. The missing scanning is a modest hygiene concern.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency and maintenance gap, though it is not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
veelasky/laravel-hashid Version * | — | — |
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.