bostondv/acf-ninja-forms

Release historydanger

The latest release was published in April 2018, about 8 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk for a WordPress integration package.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months; its last push was in February 2019, about 7 years ago. This corroborates the stale release history.

Maintainerscaution

The registry lists one publishing maintainer. Because this is a user-owned project and the repository also shows no recent activity, the narrow maintainer base adds some continuity risk.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools are configured. The build setup is present; the missing scanning reduces ongoing assurance.

Security policycaution

The repository has no security policy, leaving no documented reporting path for vulnerabilities. This is a transparency gap, although it is less severe than the demonstrated maintenance slowdown.