A small contributor base and no published security policy increase continuity and disclosure risk. Organization backing, a complete license, tests in the repository, and a modest dependency set provide useful safeguards. The package is suitable for adoption, with maintainer continuity worth monitoring.
79%
Total Score
67
100
94
75
One contributor made all commits in the last three months, producing a concentrated recent bus factor. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Only one commit was recorded in the last three months, so recent activity is present but thin. This is a mild maintenance concern rather than evidence of abandonment because the release history remains steady.
The repository uses Make and Composer, but no security-scanning tools were detected. That is a transparency and review gap, though it is not evidence of unsafe code by itself.
No repository security policy was found, leaving vulnerability reporting and disclosure expectations undocumented. The package's active organization backing partly offsets this gap but does not remove it.
Both workflows were analyzed cleanly with no untrusted checkout, script injection, or audit findings, and neither uses broad top-level write permissions. However, all four referenced actions are unpinned, which weakens build reproducibility and earns a hygiene caution.
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.