The stable version line, MIT licensing, tests, and release notes give consumers useful transparency. Its small, single-owner footprint limits evidence of long-term support.
70%
Total Score
67
100
83
83
Registry publishing access is held by one maintainer. That is not inherently unsafe, but it provides limited redundancy when considered alongside the repository's small footprint.
The package has existed since 2018 with 13 releases, but only one release in the last 12 months and a median interval of about 258 days indicate a slow maintenance cadence.
There were no commits and no active maintainers in the last three months. The recent release partly compensates for this, but the quiet period weakens evidence of ongoing maintenance.
The repository has zero stars and forks and one watcher, so there is little community evidence to supplement the maintainer's own support capacity; popularity remains supporting evidence only.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest repository hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ivopetkov/lock Version 1.* | — | — |
bearframework/bearframework Version 1.* | — | — |
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.