The package includes tests, a clear README, a declared MIT license, and a small runtime dependency set. Maintenance evidence is limited: it has only two releases, no commits in the past three months, and one registry maintainer, while the repository has no security policy or scanning.
58%
Total Score
25
100
79
83
The repository recorded zero commits and zero active maintainers in the past three months. For a package this young, that is a meaningful sign that active development may have stalled.
One person has registry publish access. The linked project is user-owned rather than organization-backed, so there is limited visible maintainer redundancy.
The package is only about five months old and has two releases, with both releases clustered within two days. That is limited evidence of sustained maintenance and lowers confidence in its maturity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than proof of unsafe code.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This modestly reduces transparency for a package that uses external Kanboard credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
carmelosantana/coqui-toolkit-kanboard Version * | — | — |
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.