stefanx/pluginx
The README has unfinished placeholder sections, and the repository has no security policy or security scanning. Its single maintainer and minimal project footprint provide little evidence of ongoing support, despite a valid license and simple dependency profile.
38%
Total Score
50
100
67
75
Health Score Breakdown
This package has only one release, published about 8 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
Only one registry maintainer is listed, which limits visible publishing redundancy. The repository is user-owned, so this is a supporting concern rather than proof that the project lacks backing.
The package includes a README and changelog, but the README contains unfinished sections such as “Insert text here,” which limits consumer guidance. The absence of tests is normal packaging practice and is not itself a gap.
Composer build tooling is present, but no security scanning tools are reported. This reduces transparency around routine security checks, though it is not evidence of malicious behavior.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a maintenance and transparency concern for a package intended for application projects.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Stefan Friedrich |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 craftcms/cms Version ^3.0.0-RC1 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.