MIT licensing, repository tests, and an unarchived organization-backed project provide useful transparency. The single unpinned workflow and absent security policy add smaller hygiene concerns.
42%
Total Score
0
70
50
The latest release was over two years ago, with no releases in the last 12 months; the earlier 10 releases show the project was once active but do not offset the prolonged stall.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the evidence of a currently inactive project.
The repository has no security policy, leaving vulnerability-reporting expectations unclear; this is a transparency gap but not a direct abandonment signal.
Version 0.7.4 is not marked prerelease, but the project remains below a stable 1.0 major version, adding some maturity uncertainty.
The only workflow was fully analyzed with no dangerous findings, but its sole action reference is unpinned; the pull_request_target trigger is not concerning without an untrusted checkout or injection sink.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
flow-php/etl Version ^0.7 || 1.x-dev | — | — |
league/flysystem Version ^3.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.