slvler/veriphone-validation
Usable with caveats: the package is licensed, documented, tested, stable, and backed by an active unarchived repository. Adoption carries maintenance risk because it has had no registry release for about 20 months, with only one recent commit from a single contributor, and it lacks a security policy.
64%
Total Score
50
100
88
80
Health Score Breakdown
The package defines a post-create-project-cmd lifecycle script, which adds install-time behavior that should be reviewed before adoption even though the signal does not show inherently dangerous workflow activity.
There have been four releases since November 2023, but the latest registry release was about 20 months ago and there were no releases in the last 12 months, indicating slowed delivery.
All recent commit activity comes from one contributor, leaving maintenance dependent on a single individual.
Only one commit was recorded in the last three months, so ongoing maintenance activity is limited even though the repository was recently updated.
Composer build tooling is present, but no security-scanning tool was detected; this is a transparency and hygiene gap rather than evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 slvler |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 2 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.