royalcms/contracts
The MIT license, small dependency surface, and organization-backed repository make the package easy to inspect. Its maintenance evidence is severely dated, and the repository does not clearly identify this package, so pinning it carries abandonment risk.
35%
Total Score
50
100
75
75
Health Score Breakdown
The latest release was about 6 years ago, with no releases in the last 12 months and only 4 releases overall. That is strong evidence of abandonment for a package a developer would depend on.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package's long release gap. No provided signal shows current maintenance activity to compensate for this.
The repository name does not match the package name and its README does not mention the package, so the repository may not clearly belong to this release. The organization backing reduces uncertainty somewhat but does not resolve the identification gap.
The linked repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a hygiene gap that adds weight to the broader transparency concerns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Royal Wang |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^7.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 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.