A single maintainer, no security scanning, and no security policy reduce confidence in long-term support. The package is clearly identified, licensed, tested, stable, and has no install-time scripts or deprecation notice.
62%
Total Score
50
100
88
83
Only one registry account has publish access, which leaves a thin publishing base. This is a maintenance resilience concern for a user-owned project rather than evidence of organization-backed support.
The package and repository are owned by the same individual account, providing clear ownership but no organizational backing to compensate for the thin maintainer base.
The package has only 3 releases and none in the last 12 months; its latest release was about two years ago. This is meaningful evidence of slowing maintenance, though the repository remains present and unarchived.
There were no commits and no active maintainers in the last 3 months, consistent with the roughly two-year release gap. This materially raises abandonment risk.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap, not a severe dependency verdict by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nguyenanhung/database Version ^3.0 | — | — |
nguyenanhung/requests Version ^3.0 | — | — |
nguyenanhung/my-crawler Version ^1.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.