gitfei1231/validate

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, indicating no recent development activity for a package released only twice.

Licensecaution

The manifest declares MIT while the artifact license file is detected as Apache-2.0. Although a license file exists, the mismatch creates legal and transparency uncertainty for adopters.

Release historycaution

The package has only two releases, both recorded on the same day, with no later release activity over roughly 11 months. This gives limited evidence of sustained maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but there is no visible community adoption to offset the thin maintenance record.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap, not proof of unsafe code.