jmrashed/purchase-key-guard
A single maintainer and no commits in the last three months reduce confidence in ongoing support. The package is licensed, tested, documented, and not deprecated, but security policy and scanning are absent.
68%
Total Score
50
86
75
Health Score Breakdown
Only one registry publishing account is listed, and the project is user-owned rather than organization-backed; this leaves limited visible publishing capacity.
The package has 19 releases over about 708 days, but only 2 in the last 12 months; this indicates a modest and recently slower release cadence.
The repository recorded no commits and no active maintainers in the last three months, which is a concrete sign that maintenance may be slowing.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap for a package that handles purchase-key validation.
The repository has no security policy, leaving no documented route for reporting vulnerabilities or describing security practices.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Rashed Zaman |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.9 | — | — |
brian2694/laravel-toastr Version ^5.59 | — | — |
Weekly Downloads
Info
- Last Published
- 5 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.