mohamednizar/moe-uuid
A single individual publishes it, and the project has no security scanning. The package includes a license, README, changelog, tests in the repository, and no install-time scripts, but its prerelease status adds uncertainty.
42%
Total Score
25
71
67
Health Score Breakdown
The last release was in May 2020, with no releases in the past 12 months despite the package being over six years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers over the past three months, consistent with the long release gap.
Only one registry account has publish access. The matching user-owned repository provides some continuity, but there is little visible publishing redundancy.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence of maliciousness.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mohamed Nizar |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 6 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.