Usable with caveats: the package is small, licensed, documented, tested, and backed by an organization, but it has had no release or repository activity for nearly two years after only two releases published about 25 minutes apart.
62%
Total Score
63
100
83
90
There have been no commits and no active maintainers in the last three months, consistent with the last push occurring nearly two years ago. For a package that may be stable, this is still the strongest abandonment concern in the available evidence.
Only one registry account has publishing access, which limits publishing redundancy. However, the linked repository is owned by an organization, which provides some compensating project backing.
The package is about 713 days old but has only two releases, both issued within roughly 25 minutes, with no releases in the last 12 months. This is a meaningful maintenance and abandonment concern.
The repository has no stars or forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these counts provide little external evidence of adoption or review.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a transparency and maintenance gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
m1/env Version ^2.2.0 | — | — |
neos/flow Version * | — | — |
platformsh/config-reader Version ^2.4.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.