paulohps/laravel-csw
Clear licensing, tests, and documentation support routine use. The project has shown no commits or active maintainers for the past three months, while its workflow uses two unpinned actions and lacks security scanning.
55%
Total Score
0
86
50
Health Score Breakdown
The repository recorded zero commits and zero active maintainers in the past three months. For a package only 154 days old, this is a meaningful sign that maintenance may have stalled.
The package defines a post-autoload-dump install-time script. Composer lifecycle execution deserves extra review because it runs during installation, although this signal alone does not establish that the script is unsafe.
The package has eight releases, but all were published on the same day and there has been no later release during its 154-day lifetime. This suggests an early burst without demonstrated ongoing release maintenance.
Composer build tooling is present, but no security scanning tools were detected. That leaves automated coverage for dependency and repository security weaker than it could be.
The repository has no security policy. This reduces transparency about vulnerability reporting and response, though it does not by itself show abandonment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Paulo Paetzold |
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
- 5 months ago
- Created
- 5 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.