The MIT license is present and the repository matches the package under organization backing. Its only release was about three years ago, with no recent commits, tests, changelog, or security policy, so maintenance risk is substantial.
46%
Total Score
50
50
50
This is the package's only release, published about three years ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
A LICENSE.md file is present and the repository also has a license file, so the release is licensed. However, the manifest says proprietary while the detected license is MIT, creating a material licensing mismatch.
The artifact has no README, tests, or changelog, and the repository reports none of these either. For a small package this is not decisive alone, but it reduces transparency and confidence in future maintenance.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
quantaforge/support Version ^1.0.0 | — | — |
quantaforge/contracts Version ^1.0.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.