Its six runtime dependencies add maintenance surface, and only one registry publisher is listed. The repository could not be found, so source activity and provenance remain unverifiable.
42%
Total Score
50
50
50
Only two releases exist, with the latest in June 2021 and no release in over five years. This is strong evidence of abandonment risk for a library dependency.
Six runtime dependencies create meaningful maintenance and compatibility surface for a small library, with no provided evidence that this burden is actively managed.
One registry publisher is listed, which provides little redundancy if that maintainer becomes inactive; registry access does not prove current development activity.
Version 0.2.0 is not marked prerelease, but the package has never reached a stable major version, limiting maturity evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
stk2k/util Version ~0.2 | — | — |
knot-lib/config Version ~0.3 | — | — |
stk2k/collection Version ~0.1 | — | — |
stk2k/file-system Version ~0.1 | — | — |
knot-lib/exception Version ~0.3 | — | — |
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.