38%
Total Score
unhealthy
Risky: nearly six years without a release or commit activity, plus a repository that does not identify this package.
The latest release was nearly six years ago, with no releases in the last 12 months. The 11-release history shows prior activity but does not compensate for the prolonged release gap.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance.
The package includes a README, but it is only 26 characters and contains a heading without usage guidance; the absence of tests and a changelog in the published artifact is normal packaging practice. A GitHub release exists for this version, which provides some release traceability.
The repository name does not match the package name and its README does not mention the package, leaving uncertainty that it is the intended source repository. This is a transparency concern even though the mismatch could reflect packaging structure.
The linked repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. No other provided signal compensates for this transparency gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
swango/db Version ^1.0 | — | — |
swango/cache Version ^1.0 | — | — |
swango/model Version ^1.0 | — | — |
swango/stdlib Version ^1.2 | — | — |
swango/environment 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.