ecotone/tempest

The package has a substantial README, repository tests, organizational ownership, and a rapid release cadence. Its beta status, single active contributor, licensing split, and absent security policy leave less assurance for a foundational integration.

Latest 2.0.0-beta.1

Packagist

67%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

License

The artifact contains license files and detected Apache-2.0 text, so the release is licensed. The manifest's additional proprietary declaration does not cleanly align with the detected Apache-2.0 license and warrants checking the enterprise terms.

Repo bus factor

One contributor made all 14 commits in the last three months, creating a real continuity risk. Organizational ownership provides some handoff capacity, but no second active contributor is shown.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. For an integration package, that is a modest transparency and maintenance gap rather than evidence of unsafe code.

Security policy

The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package handling application integration and database-related features.

Version stability

Version 2.0.0-beta.1 is explicitly a prerelease, so its API and behavior may still change. Only 1 of the 15 recent releases was a prerelease, which partly limits the concern but does not remove beta risk.