Concept stack brick: error handling (Whoops)
58%
Total Score
caution
One day of history, with no tests, README, or security policy, makes long-term maintenance uncertain despite active publishing.
The package declares 12 runtime dependencies and no development dependencies, creating a relatively broad runtime surface and offering little evidence of an in-project test or development setup.
The artifact has no README, tests, or changelog, and the repository reports none either. Missing tests and release documentation reduce transparency for a library consumers must integrate, though the absence of tests in a published artifact alone is normal.
The package is only 1 day old, despite 6 releases in that period; this shows active initial publishing but provides no evidence of sustained maintenance yet.
The repository has 0 stars, forks, and watchers. For a package only 1 day old this is weak supporting evidence rather than a standalone health failure.
Composer is used for the build, but no security scanning tool is configured. The missing scanning is a transparency gap, while Composer itself is appropriate for this PHP package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^3 | — | — |
league/container Version ^5.1 | — | — |
php-concept/stack Version ^2.0 | — | — |
php-concept/core-2 Version ^1.0 | — | — |
php-concept/brick-http Version ^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.