aeunius/laravel-peru-rules
A single maintainer and no security policy leave limited continuity and disclosure coverage. The repository has tests, a changelog, readme, and read-only workflow permissions, but the project is too new to establish sustained maintenance.
62%
Total Score
50
100
86
67
Health Score Breakdown
Only one registry account has publish access, which limits publishing continuity; the linked repository is user-owned, so there is no organization backing shown to compensate for that thin base.
The registry namespace and repository are both owned by the same individual account, which supports ownership consistency but does not provide organizational continuity.
The package is 0 days old with four releases issued within hours, so its release and maintenance record is not yet established.
There were zero commits and zero active maintainers in the last three months, but the repository is newly created, making this more an unproven maintenance record than evidence of abandonment.
The repository uses Make and Composer build tooling, but no security scanning tools are present, leaving a modest security-process gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Alejandro Gonzales Sarmiento |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/contracts Version ^12.0|^13.0 | — | — |
illuminate/validation Version ^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16.2 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 2 days 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.