The organization-backed repository includes tests, release notes, and a matching README. The license metadata conflicts with the Apache-2.0 file, adding adoption uncertainty.
47%
Total Score
75
100
81
75
The artifact contains an Apache-2.0 license file, but the manifest declares a proprietary license. This mismatch creates legal and transparency uncertainty despite the presence of a recognizable license file.
This package has only one release, published about 8 years ago, with no releases in the last 12 months. That is a substantial maintenance and abandonment concern, although the repository is not archived.
No commits and no active maintainers were recorded in the last 3 months. Combined with the single-release history, this supports a meaningful abandonment concern.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest repository hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy. For a small integration module this is a transparency gap, though it is less significant than the stale release history.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/monitoring-extension Version ^1.0.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.