teamq-ec/teamq-doctrine-behaviors

Release historycaution

The package has only two releases across about 2 years and 4 months, with no release in the last 12 months. That suggests limited maintenance capacity, though the latest release is a stable major version.

Repo commit activitycaution

There were no commits and no active maintainers in the last 3 months. Combined with no releases in the last 12 months, this is meaningful evidence of stalled maintenance.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counters provide little external evidence of maturity or community support.

Repo toolingcaution

The project uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. For a dependency project this weakens vulnerability-reporting transparency, although it does not by itself indicate abandonment.