wazza/laravel-db-encryption
Tests, release notes, licensing, and a security policy make the project reasonably transparent. Maintenance has gone quiet, and its workflow dependencies are not pinned, so future fixes and builds deserve extra scrutiny.
62%
Total Score
0
86
100
Health Score Breakdown
There were no commits and no active maintainers in the last three months, and the last recorded push was about eight months before collection. This is a meaningful maintenance and abandonment concern for a security-sensitive library.
The package has three releases across about 15 months, with only one release in the last 12 months and a roughly four-month median interval. This indicates a modest, somewhat slow release cadence rather than abandonment by itself.
The assessed release is a stable v1.0.0, but two-thirds of recent releases were prereleases. The stable version is positive, while the recent prerelease-heavy history adds some uncertainty.
All four analyzed action references are unpinned, weakening build reproducibility and increasing exposure to changing action code. The audit was complete and found no dangerous triggers, untrusted checkouts, script injection, or high-confidence audit findings, which keeps this at caution rather than danger.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Warren Coetzee |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/console Version ^12.0 | — | — |
illuminate/support Version ^12.0 | — | — |
illuminate/database Version ^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 months ago
- Created
- 1 year 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.