aplia/content-tools
The MIT license, readable documentation, and release notes make integration easier. Organizational ownership and a clean package tree add confidence, but ongoing support is uncertain.
55%
Total Score
75
100
88
75
Health Score Breakdown
The package has 61 releases since 2016, but it has had no release in nearly five years and none in the last 12 months, indicating likely stagnation.
There were no commits and no active maintainers in the last three months, consistent with the release history and raising meaningful maintenance risk.
Composer is used for builds, but no security scanning tools are present, leaving a transparency and maintenance-hygiene gap.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Aplia dev-team |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 aplia/support Version ^1.0 | — | — |
cash/lrucache Version 1.0.0 | — | — |
composer/composer Version >=1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 9 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.