mlukman/gitsync

Release historydanger

The package has had no releases in about eight years, despite 29 releases historically. This strongly raises abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.

Licensecaution

A license file is present, but the manifest declares GPL-1.0-or-later while the artifact license text was detected as GPL-3.0. That mismatch reduces licensing clarity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap, though not evidence of a security incident by itself.

Security policycaution

The repository has no security policy, leaving no documented channel or process for handling vulnerabilities in a package that manages server directories and Git repositories.