jenky/transmit

Release historydanger

The package has had no releases in more than four years, with zero releases in the last 12 months. This is meaningful abandonment risk for a Laravel integration package.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this weakens confidence that issues or compatibility changes will be addressed.

Project backingcaution

The registry namespace and repository are owned by the same individual account. This is coherent ownership evidence, but it does not provide organization-level maintenance capacity.

Repo popularitycaution

The repository has no stars or forks and only one watcher. Low popularity is not decisive, but it provides little supporting evidence of active community use alongside the stale activity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.