The package includes a clear README, repository tests, a focused dependency set, and an active organizational home. Clarify the Apache-2.0 versus proprietary licensing before adoption, and expect some beta-version churn.
68%
Total Score
83
79
50
The manifest declares the package proprietary while artifact and repository license files are detected as Apache-2.0. The mismatch needs clarification before relying on the package's licensing terms.
One contributor made all 14 commits in the last 3 months, creating a concentrated maintenance dependency. The organization-owned repository provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and assurance gap, not evidence of an unsafe release by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a transport integration package.
Version 2.0.0-beta.1 is a prerelease, so compatibility may still change, although prereleases represent only 5% of recent releases.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ecotone/ecotone Version ~2.0.0-beta.1 | — | — |
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.