A complete README, extensive unit tests, and a stable MIT license support adoption. The single maintainer and absent security tooling leave limited evidence of long-term resilience.
64%
Total Score
50
88
50
The package has one release, published about 13 months ago, with no releases in the last 12 months. That is limited evidence of ongoing maintenance for a persistence library.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the one-release history, this is meaningful evidence of weak recent maintenance.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a release-blocking issue.
The repository has no security policy. For a library that handles database persistence, this leaves vulnerability-reporting expectations unclear.
The only workflow was fully analyzed with no dangerous triggers or audit findings, but its one action reference is unpinned and the workflow has no top-level permissions block. These are limited workflow-hygiene concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
subtext/collections Version ^1.0.0 | — | — |
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.