The repository is small but organized, with tests, clear licensing, and a matching source project. A single maintainer and no recent registry releases limit confidence, although the organization-backed repository was pushed recently.
68%
Total Score
67
100
88
83
Only one registry account has publish access, which limits publishing redundancy. The organization-backed repository provides some compensation, so this is a modest concern rather than a severe risk.
The package has had no registry release for more than five years, despite 11 releases overall and a historically short median interval of about 3 days. This weakens confidence in the published release's ongoing maintenance.
There are no new or closed issues or pull requests in the last month, with one pull request open. This provides little evidence of active project-level coordination.
Composer build tooling is present, but no security-scanning tool was detected. That is a repository hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, reducing transparency around vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
canvass/canvass-core Version ^1.02 | — | — |
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.