pith/doctrine-migration-integration

Release historydanger

This is the only release, published about 2 years and 5 months ago, with no releases in the last 12 months. That is substantial evidence of a dormant project for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, providing no evidence of current maintenance capacity. The repository is not archived, but that does not offset the lack of activity.

Licensecaution

The manifest declares MIT, while the artifact license file is detected as MPL-2.0. The release is licensed, but the mismatch creates a meaningful transparency and compliance concern.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That raises uncertainty about whether the linked repository is actually the package's source.

Repo toolingcaution

Composer is used for builds, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.