The single registry maintainer and absent security scanning reduce confidence in ongoing support. Tests, a changelog, release notes, and a matching repository provide useful transparency.
58%
Total Score
50
80
75
The manifest declares MIT while the detected license files identify BSD-3-Clause; the release is licensed, but the mismatch creates avoidable legal ambiguity.
Only one registry account can publish releases, which creates a thin publishing base. The repository is owned by an organization, providing some backing but not evidence of active maintenance by itself.
This is the package's only release, published nearly 10 years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance, though the repository was pushed more recently.
The repository recorded no commits and no active maintainers in the last 3 months. This supports the concern that development has effectively stalled.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a module that processes traffic and blocking rules.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.