ufee/amoapi-v4
The project relies on one active contributor and has no published security policy, which raises continuity and response concerns. MIT licensing, tests, release notes, and frequent recent releases provide useful transparency and maturity.
80%
Total Score
67
100
94
83
Health Score Breakdown
The repository is owned by the same individual user as the package namespace, so there is no apparent organization backing to offset the concentrated contributor base.
All 11 recent commits came from one contributor, leaving maintenance highly dependent on a single person and increasing continuity risk.
Composer build tooling is present, but no security scanning tools were detected, leaving automated security coverage unclear.
The repository has no published security policy, so vulnerability reporting and response expectations are not documented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Vlad Ionov |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 2 days 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.