jan-wieland/pim-ck-editor
Its documentation is too thin for a bundle developers must configure, and the repository has no security policy or scanning. The single maintainer is a manageable continuity risk for a young project.
60%
Total Score
50
100
81
83
Health Score Breakdown
One registry maintainer, Jan Wieland, publishes the package, leaving a narrow continuity base. The matching repository ownership provides some context but does not establish broader maintenance capacity.
The artifact includes a README, but it is only 16 characters long and contains just the package heading. For a WYSIWYG editor bundle, this provides little integration guidance.
The package is 117 days old and has only one release, so there is little release history to establish maintenance reliability. Its recent first release limits how strongly this should count against it.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, with its last push on May 26, 2026. That leaves no observed ongoing maintenance after the initial release.
The repository uses Composer, which supports reproducible package management, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jan Wieland |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 pimcore/pimcore Version ^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 4 months 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.