It has a clear README, changelog, matching source repository, and declared license. The repository is not archived, but it lacks a security policy and automated security scanning.
57%
Total Score
50
86
67
The package has 22 releases and a roughly 20-day median release interval, but it has had no release in about 21 months. That long silence lowers confidence in ongoing maintenance.
The repository recorded no commits and no active maintainers in the last 3 months, reinforcing the extended release gap. This suggests maintenance may have stalled.
Composer is used for builds, which is appropriate, but no security-scanning tools were detected. That reduces evidence of proactive dependency and code-risk monitoring.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and response-readiness gap.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 3 of its action references are unpinned. That leaves the build exposed to moving action versions.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nguyenanhung/my-debug Version ^4.0 || ^3.0 | — | — |
nguyenanhung/requests Version ^4.0 || ^3.0 | — | — |
nguyenanhung/basic-firewall Version ^2.0 | — | — |
nguyenanhung/codeigniter-framework Version ^3.2 | — | — |
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.