asconsulting/member_autoactivate

Maintainerscaution

Only one registry account has publishing access, leaving limited publishing redundancy. This is a resilience concern, although registry access alone does not establish the project's actual maintenance activity.

Release historycaution

The package has existed for over seven years but only has two releases, with one release in the last 12 months and a median interval of about seven years. The recent release helps, but the sparse history limits confidence in sustained maintenance.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months. The recent push associated with the release is a compensating sign, but ongoing activity currently appears limited.

Repo toolingcaution

The repository uses Composer for its build, which fits the package ecosystem, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy, so it gives users no documented process for reporting or handling vulnerabilities.