20steps/commons-ensure-bundle

Release historydanger

The package has had no releases in nearly eight years, despite four releases since 2016; this is substantial evidence of abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance.

Repo popularitycaution

The repository has no stars and only one fork, so there is little community evidence to offset the maintenance concerns, although popularity is supporting evidence only.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured; the missing scanning is a modest hygiene concern rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented; this is a moderate transparency gap for an otherwise inactive project.