anexia/neos-monitoring
The MIT license, focused dependency set, and organization-backed repository make the package transparent to inspect. It lacks security scanning and a security policy, increasing maintenance risk for a monitoring plugin.
43%
Total Score
100
67
50
Health Score Breakdown
The package has had only two releases, both in October 2018, with no release in more than seven years. This is strong evidence of abandonment risk despite the stable version.
Composer is used for builds, but no security scanning tools are configured. For a monitoring plugin that may be deployed into a production application, this leaves a meaningful maintenance and review gap.
The repository is not archived, which is a positive mitigating signal, but it was last pushed in April 2021 and has therefore been inactive for roughly five years.
The repository has no security policy, reducing transparency about vulnerability reporting and maintenance expectations. This adds concern but is less serious than the long release and commit inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Nikita Bernthaler |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/flow Version >=4.0 | — | — |
composer/semver Version ~1.4.2 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.