royalcms/container
The MIT license, stable versioning, and small dependency surface reduce adoption friction. The lack of a security policy leaves little additional transparency for a dependency that has seen no recent maintenance.
40%
Total Score
75
100
75
75
Health Score Breakdown
Only three releases exist, and none were published in the last 12 months; the latest release was about six years ago, indicating likely abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history's prolonged inactivity.
The repository name does not match the package name and its README does not mention the package, so the source-package relationship is unclear despite the linked repository.
The repository has no security policy, reducing transparency for vulnerability reporting and response; the package's MIT license does not compensate for this operational gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Royal Wang |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 royalcms/contracts Version ^7.0 | — | — |
illuminate/container 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.