mpyw/easycrypt

Project backingcaution

The registry namespace and repository are both owned by the same individual, so the package has direct ownership alignment but no organizational backing. This leaves a relatively narrow maintenance base.

Release historycaution

The project is mature, with releases dating back to 2016, but it has made no release in the last 12 months and has only seven releases overall. This indicates a real maintenance concern, though the latest release is recent enough that abandonment is not established.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Together with no release in the last 12 months, this lowers confidence in ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a modest transparency and maintenance gap, not evidence of an unsafe release by itself.

Security policycaution

No security policy is published in the repository. That makes vulnerability reporting and response expectations less transparent, although the repository's tests and documentation provide some compensating project structure.