codefog/contao-disqus
The package has a clear README and a source repository that matches its name and contents. Its last release and repository push were in December 2017, with no recent commits, and the repository has no security policy or scanning tools. The LGPL-3.0+ declaration and organization backing provide some transparency.
38%
Total Score
50
75
50
Health Score Breakdown
Only two releases exist, and the latest was published in December 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a maintained CMS extension.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no observed maintenance.
Composer is used for the build, but no security-scanning tools are configured. This is a hygiene gap that adds some transparency concern, though it is less significant than the long maintenance gap.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This modestly reduces transparency but does not by itself show that the release is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Codefog |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 contao/core Version >=3.2 | — | — |
contao-community-alliance/composer-plugin Version 2.* | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 11 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.