test PaymentService Lib
34%
Total Score
unhealthy
Risky: six years without a new release or repository activity, with a one-person project and a repository/package mismatch.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided maintenance signal offsets this lack of recent activity.
A single registry maintainer provides a thin publishing base, which increases continuity risk for a package with no recent release or commit activity. This is only supporting evidence because registry access does not prove who actively maintains the project.
The package has no README, which is a documentation gap for a library consumers must integrate. The absence of tests and a changelog in the artifact is normal packaging practice, while the repository does contain a test file.
The package has had only one release, published about six years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, although the release is stable and not deprecated.
The repository name does not match the package name, and no README mention was collected, so the linkage is less transparent. A monorepo subpackage could explain the name difference, but the available evidence does not establish that.
We didn't find any vulnerabilities for this package.
| Version | Published | Vulnerabilities |
|---|---|---|
| v1.1 | 5 Jul 2020 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
No direct dependencies.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.