The package is tiny, has one runtime dependency, and declares MIT licensing. Its repository is not archived, but documentation and project safeguards are sparse.
59%
Total Score
50
100
75
83
The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the absent README is a modest consumer-transparency gap for a logging library.
Only one release exists, published 283 days ago, with no subsequent releases. That leaves the package's longer-term maintenance record unproven.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the single-release history, this weakens evidence of active maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a small logging library this is a transparency gap, but it is not by itself a severe dependency risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
appkit/async 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.