A recent release and clear repository ownership provide useful support, while the package remains lightly maintained and lacks a published security policy. Confirm that the OSL-3.0 repository license matches your intended use despite the proprietary manifest declaration.
67%
Total Score
75
100
81
83
The manifest declares a proprietary license, while the repository LICENSE.txt is identified as OSL-3.0. That mismatch creates a meaningful legal and transparency concern even though a license file is present.
The package has existed for about 3 years and 5 months with 8 releases, including one in the last 12 months. The long median interval indicates a modest release cadence rather than strong ongoing activity.
There were zero commits and zero active maintainers in the last 3 months. This suggests limited current maintenance capacity, although the recent release provides some compensating evidence.
Composer build tooling is present, but no security scanning tools were detected. For a module focused on dependency integrity, that missing security tooling is a modest transparency gap.
The repository has no published security policy. That makes vulnerability reporting and response expectations less clear for a security-focused integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sansec/composer-integrity-plugin Version ^0.2.0 | — | — |
hyva-themes/module-magento2-admin Version ^1.1 | — | — |
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.