MIT licensing, stable versioning, and a minimal package structure make the release straightforward to inspect. Its repository has had no recent commits, and the package-to-repository identity is not clearly established.
55%
Total Score
50
100
71
75
The package has five releases, but the latest was on January 11, 2023, with no releases in the last 12 months. This indicates a long maintenance gap for a package that may need compatibility updates.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this reduces confidence that compatibility issues will be addressed promptly.
The repository name does not match the package name and its README does not provide a package mention. That leaves the ownership relationship less clear than expected, even though the repository URL is package-specific.
The repository uses Composer for builds, which fits the package ecosystem, but it reports no security scanning tooling. This is a modest transparency gap rather than a severe dependency risk.
The linked repository is not archived, although its last push was on January 11, 2023, which is consistent with the observed maintenance gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version * | — | — |
magento/module-eav Version * | — | — |
magento/module-store Version * | — | — |
magento/module-catalog Version * | — | — |
mateuszmesek-magento2/module-document-data-eav-api Version ^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.