huaiyang/breakpoint
The repository has no security policy or security scanning, while one maintainer provides little redundancy. Its four-file layout is easy to inspect, but offers little evidence of broader project support.
38%
Total Score
0
33
50
Health Score Breakdown
Only two releases were published, with none in the last seven years; the latest release dates to May 2019. This strongly indicates abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push having occurred over seven years ago.
The package has no declared license, detected license, or license file in the artifact or repository. This creates a real legal and transparency concern for adoption.
Composer is used as a build tool, which fits the package ecosystem, but no security-scanning tooling is present. The missing scanning reduces maintenance transparency slightly.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a hygiene and maintenance gap rather than evidence of malicious behavior.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 huaiyang |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.