The package is clearly scoped as a Composer type-definition metapackage, with a matching repository and no install scripts. Its release history is too new to establish maintenance, and the repository has no security policy or scanning.
68%
Total Score
83
100
89
83
This is the first release, published 0 days ago, so there is no release cadence or maintenance history to assess. That is a meaningful maturity gap for a dependency, though it may simply reflect a newly created package.
There were 0 commits and 0 active maintainers in the last 3 months. Given that the package was released 0 days ago, this is mainly an absence of history rather than proof of abandonment, but it limits confidence.
The repository uses Composer build tooling, which fits the package ecosystem, but it reports no security scanning tools. That is a modest transparency and maintenance-hygiene gap.
The repository has no security policy. For a small type-definition metapackage this is not severe, but it leaves vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
tyhpdef/brianium-paratest-impl Version ~7.24.1.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.