myservices/rpc
The package has a clear MIT license, tests, and a small dependency surface. There is no security policy or automated security scanning, so future fixes and oversight are uncertain.
38%
Total Score
0
100
79
50
Health Score Breakdown
The latest release was published in March 2018, with no releases in the following eight years and seven releases overall. This strongly indicates the package is no longer maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The inactive development signal materially raises abandonment risk.
Composer is used for the build, but no security-scanning tools are configured. That leaves dependency and code-security checks less visible and less repeatable.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for an RPC library.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Crazy |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.