code-tool/jaeger-client-symfony-bridge

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. This is the strongest concern because it suggests maintenance may have stalled, although the current registry release partially offsets it.

Release historycaution

The package has existed for about 8 years with 162 releases, but only 2 releases in the last 12 months, indicating a slower recent cadence despite the new assessed release.

Repo issue activitycaution

There are only 2 open issues, no open pull requests, and no issue or pull-request activity in the last month. The small backlog is positive, but the lack of recent activity is consistent with limited maintenance.

Repo popularitycaution

The repository has only 11 stars and 7 forks, indicating a small adoption and contributor footprint. Popularity is supporting evidence rather than a decisive health verdict, so this lowers confidence in long-term support modestly.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning coverage is a maintenance and transparency gap, though it is not by itself severe.