maxiviper117/laravel-access
The package is well documented, licensed, and backed by tests, release notes, and automated checks. Its security policy is absent, while several workflows grant broad write access despite having no detected unsafe trigger or sink.
68%
Total Score
50
100
81
50
Health Score Breakdown
One registry maintainer is consistent with a user-owned project, but it leaves publishing continuity dependent on a single person.
The repository is owned by an individual rather than an organization, so the single-maintainer and single-contributor risks are not offset by visible organizational backing.
Four releases in about four months, with a median interval of roughly 5 days, show active early development; the short project history limits maturity evidence.
All recent commits came from one contributor, creating a concentrated maintenance dependency with no demonstrated handoff capacity.
Only two commits were recorded in the last three months from one active maintainer; this is limited maintenance evidence for a young authorization library.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Maxiviper117 |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^11.0||^12.0||^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 4 months 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.