agile/domain

The small dependency surface, MIT license, and matching source repository reduce adoption friction. The project has no security policy or security scanning, leaving little evidence of ongoing operational care.

Latest 1.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published in March 2016, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency released nearly a decade ago.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last release. No newer activity is provided to offset that concern.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The limited tooling provides little additional evidence of release or security oversight.

Repository archived

The repository is not archived, which avoids an explicit abandonment marker, but its last push was in August 2016 and does not compensate for the prolonged inactivity.

Security policy

No security policy was found in the repository. This is a transparency and response-process gap, especially for a package that has not shown recent maintenance.