claroline/net-theme-bundle
Its organization ownership, stable versioning, and small runtime dependency surface provide useful context. The missing security policy and repository/package naming mismatch reduce transparency, while the long maintenance gap remains the main concern.
38%
Total Score
50
100
75
75
Health Score Breakdown
The latest release was in February 2016, with no releases in the last 12 months despite 15 historical releases. This long release gap is strong evidence of abandonment risk.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's prolonged release inactivity.
The linked repository name does not match the package name and its README does not mention the package, so package ownership is less transparent even though the repository is under the same organization.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest process gap rather than evidence of immediate unfitness.
The repository has no security policy. For a reusable framework bundle, this leaves vulnerability reporting and maintenance expectations unclear.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Claroline development team |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 claroline/core-bundle Version >=5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 12 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.