The source repository includes tests, explicit release notes, and a matching project, which support transparency. A missing security policy and absent automated security scanning leave maintenance safeguards weaker.
57%
Total Score
75
100
81
75
The package has had no registry release for nearly 7 years, with no releases in the last 12 months. Its earlier six-release history shows past activity but does not offset the prolonged release gap.
The repository recorded no commits or active maintainers in the last 3 months, indicating limited current maintenance. This is concerning, though the repository is not archived and was pushed in November 2023.
Composer is used as a build tool, supporting reproducible package installation, but no security scanning tool was detected. The missing scanner is a modest transparency and maintenance gap rather than evidence of unsafe code.
The linked repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0 | — | — |
docalist/docalist-core Version ^3.4.0 | — | — |
docalist/docalist-data Version ^4.2.0 | — | — |
docalist/docalist-search Version ^4.2.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.