codeq/jumpmarkers
Documentation and release notes make integration clear, and the organization-backed repository remains active enough to be credible. Security automation is limited, so pin this version and verify compatibility with your Neos stack.
62%
Total Score
75
100
88
75
Health Score Breakdown
The package has nine releases since September 2021, but none in the last 12 months; the latest registry release was in May 2023. This indicates slowed maintenance and warrants caution.
The repository recorded zero commits and zero active maintainers in the last three months. This weakens evidence of current maintenance, although the 2025 push and release history provide some compensation.
Composer build tooling is present, but no security scanning tools were detected. The absence of security automation is a modest transparency and maintenance gap, not a standalone severe risk.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a hygiene gap rather than evidence that the package is unsafe.
No GitHub Actions workflows were analyzed, with zero workflows present and no audit failures or risky findings. This avoids workflow exposure, but it also provides no automated CI or security-maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Roland Schütz |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/neos Version ^7.0 || ^8.0 || dev-master | — | — |
carbon/eel Version ^1.0 || ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 4 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.