Tests, a stable MIT declaration, and organization backing provide useful context, but the single maintainer and missing security policy leave limited oversight. The workflow is audited cleanly, though its one action is unpinned.
42%
Total Score
50
75
67
The package has had only two releases, both in May 2020, with no release in more than six years. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and indicating no current maintenance.
The repository name does not match the package name and its README does not mention the package, making package ownership and source alignment less transparent.
The repository has no security policy, leaving no documented channel or process for reporting and handling vulnerabilities.
The single workflow was fully analyzed with no dangerous findings, but its one action reference is unpinned, leaving that build dependency exposed to moving upstream code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phore/filesystem Version * | — | — |
phore/http-client Version * | — | — |
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.