The focused client has clear packaging, licensing, and release documentation, with organizational backing. Recent repository work is sparse and comes from one contributor, while workflow references are not pinned and no security policy or scanning is present.
70%
Total Score
67
100
94
75
All recent commits came from one contributor, creating concentration risk; organization ownership provides some handoff capacity but does not remove the lack of currently active contributors.
Only one commit was recorded in the last three months, indicating limited recent maintenance despite the recent release history.
The project uses Make and Composer build tooling, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
No repository security policy was found, reducing clarity about vulnerability reporting and maintainer response practices.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, or audit findings. However, all four action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
async-aws/core Version ^1.9 | — | — |
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.