chiron/http-exceptions

The repository is not archived, carries a clear MIT license, and has a useful README with repository tests. Its workflow uses four unpinned actions and the project has no security policy, leaving avoidable maintenance and build-trust gaps.

Latest 2.03

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly five years, with zero releases in the last 12 months. Its earlier release cadence and eight total releases show a real project history, but do not offset the current inactivity.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for several years. The repository's non-archived status is only partial reassurance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For this small library that is a modest process gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though not a standalone reason to reject the dependency.

Workflow audit

The sole workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, and it does not grant top-level write permissions. However, all four action references are unpinned, creating a build reproducibility and update-trust weakness.