edofre/laravel-ns-api
The README, MIT licensing, and release notes make the package straightforward to inspect and integrate. Install-time scripts and the absence of security scanning add operational uncertainty for a library this old.
35%
Total Score
25
75
67
Health Score Breakdown
This is the only release, published about 9 years ago, with no releases in the last 12 months. That strongly suggests the package is abandoned, despite the lack of registry deprecation.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package having received no maintenance since its initial release.
The package runs post-install and post-update scripts, which add installation-time behavior that consumers must account for, though this is not severe on its own.
One registry maintainer is reasonable for a user-owned project, but it provides little redundancy when the repository also shows no recent activity.
Composer build tooling is present, but no security scanning tools were detected. For an old package, that leaves its maintenance and vulnerability checks less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Edo Freriks |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version >=6.2.2 | — | — |
laravel/framework Version 5.3.* | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.