The project has one active contributor and the linked repository does not clearly identify this package. Frequent recent releases, an MIT license, useful documentation, and organizational ownership partly offset those concerns.
70%
Total Score
83
100
75
75
All 16 recent commits came from one contributor, giving the project a complete single-maintainer dependency risk. Organizational ownership provides some capacity for handoff but does not remove the concentration concern.
The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less transparent and warrants caution.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little external validation or visible community support.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency gap, not evidence of unsafe code by itself.
No repository security policy was found. This weakens the project's stated process for handling vulnerabilities, though it does not by itself indicate abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version ^6 || ^7 || ^8 | — | — |
kaystrobach/backend Version * | — | — |
kaystrobach/bootstrap Version * | — | — |
matomo/device-detector Version ^6.3 | — | — |
kaystrobach/visualsearch Version * | — | — |
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.