dima-bzz/laravel-config-writer
Tests, documentation, release notes, and licensing are all in place. The build workflow has an unpinned container image and lacks security scanning, which weakens publishing hygiene.
52%
Total Score
0
83
67
Health Score Breakdown
The package has had no release in nearly five years, with zero releases in the last 12 months. This is strong evidence of a dormant project, although the existing release is documented and not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The repository has no security policy, so consumers have no documented channel or process for reporting security issues. This is a transparency gap, but it is secondary to the maintenance evidence.
All 8 action references are unpinned, and the audit found a high-confidence unpinned container image in php-cs-fixer.yml. The workflows have no untrusted checkout or script-injection findings, which limits the concern to build hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dmitry Mazurov |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/config Version ^7.0|^8.0 | — | — |
illuminate/support Version ^7.0|^8.0 | — | — |
illuminate/filesystem Version ^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 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.