There is no security policy or security-scanning tool, which weakens transparency for a compliance-focused integration. The package is licensed, documented, tested in the repository, and has no install scripts.
61%
Total Score
50
79
75
The package is only 63 days old and has two releases, both published within a very short initial burst; this provides little evidence of sustained maintenance.
One contributor holds 100% of the two recent commits, leaving maintenance dependent on a single person in this user-owned project.
Only two commits were recorded in the last three months, all from one active maintainer. That is some recent activity but weak evidence of ongoing maintenance capacity.
Composer build tooling is present, but no security-scanning tool was detected. For a compliance-oriented integration, that is a meaningful transparency and maintenance gap.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package that handles audit and compliance data.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^13.0 | — | — |
illuminate/support Version ^13.0 | — | — |
illuminate/contracts Version ^13.0 | — | — |
laravel-chronicle/core Version 1.13.0 | — | — |
kanvigo/audit-contracts Version ^0.1.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.