svenjuergens/disable_beuser
A single individual maintains the package, and the repository has no security policy or automated security scanning. The recent 5.1.0 release, clear release notes, stable versioning, and simple dependencies provide useful counterweight.
72%
Total Score
50
100
88
83
Health Score Breakdown
Only one registry account has publish access. That is a thin publishing base and creates some continuity risk, although the repository and package are consistently tied to the same individual.
The repository is owned by the same individual represented by the registry namespace, rather than an organization. This makes the single-maintainer limitation more relevant to continuity risk.
The package has existed for about 9 years and released once in the last 12 months, with a median interval of about 249 days. The recent release supports continued maintenance, but the slow cadence warrants modest caution.
The repository recorded zero commits and zero active maintainers in the last 3 months. The recent release partly offsets this, but the current lack of ongoing activity is a maintenance concern.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Sven Juergens |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 typo3/cms-core Version ^13.4 || ^14.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 9 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.