emaia/laravel-d4sign
Documentation, tests, licensing, and security reporting are in place. Workflow hygiene and the single-maintainer profile add risk, while the old release history makes long-term support uncertain.
44%
Total Score
25
75
100
Health Score Breakdown
Only two releases exist, with the latest published in August 2022 and none in roughly four years. This is strong evidence of abandonment risk for a dependency.
There were no commits and no active maintainers in the last three months. Combined with the old registry release, this supports a meaningful maintenance concern.
The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible backing when combined with a single registry maintainer and inactive recent development.
The repository has only 2 stars and no forks or watchers, indicating limited visible adoption. Popularity is supporting evidence rather than a health verdict, so this is a modest concern.
Version 0.1.1 is not a stable-major release, so its API maturity is limited. The available release notes and repository evidence provide some context but do not offset the early version line.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ednilson Maia |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.4 | — | — |
illuminate/contracts Version ^9.0 | — | — |
spatie/laravel-package-tools Version ^1.9.2 | — | — |
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.