jtc-solutions/helpers
Tests and a readable README provide useful consumer evidence, and the package is backed by an organization. The proprietary licensing, absent security scanning, and 17 months without maintenance make long-term adoption a liability.
46%
Total Score
75
100
71
67
Health Score Breakdown
The manifest declares a proprietary license, with no license file detected in either the package or repository. That creates a significant legal and transparency concern for an open-source dependency.
The package has only two releases, both within about five days, followed by no release in roughly 17 months. This provides little evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. The repository is not archived, but current maintenance capacity is unproven.
Composer and Make are used for builds, but no security-scanning tools are present. This is a maintenance and assurance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a reusable PHP library, though it is not severe on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 David Jungman |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ramsey/uuid Version ^4.7 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.