This display the coupon list in my account page
38%
Total Score
unhealthy
One release nearly three years ago, no recent commits, and a repository that does not identify the package make maintenance uncertain.
The package has had only one release, published 1074 days ago, with no releases in the last 12 months. This is strong evidence of an inactive release line.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since the only release. No provided maintenance signal compensates for this inactivity.
The manifest declares GPL-3.0 and proprietary licensing, so the release is not unlicensed. No detected license text is available to clarify how those declarations apply, which leaves some licensing ambiguity but not a missing-license gap.
The package has a README, but it contains only seven characters (`# test1`), offering essentially no consumer or maintenance documentation. The missing tests and changelog are normal for a published artifact, while the GitHub release is a modest positive.
The repository name does not match the package name and its README does not mention the package. A subpackage can legitimately use a monorepo, but no such relationship is shown here, so package ownership is unclear.
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.