This release appears healthy and suitable to depend on: it is actively and frequently released, uses a stable non-prerelease version, is not deprecated, has a current non-archived repository, an MIT license, a small runtime dependency set, and no install-time lifecycle scripts. The main concerns are that all 45 recent commits came from one contributor and the repository lacks security scanning and a security policy, which reduce resilience and transparency; however, the repository is organization-owned, has current activity, and contains tests even though the package artifact does not include them.
82%
Total Score
83
100
94
90
One contributor made all 45 commits during the last three months, creating a material single-maintainer continuity risk. Organization ownership provides some capacity for handoff, but no second active contributor is shown.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning lowers supply-chain hygiene confidence without independently indicating abandonment.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is less severe than evidence of unsafe workflows or abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
tempest/highlight Version ^2.11.4 | — | — |
symfony/var-dumper Version ^7.1|^8.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.