net_bazzline/component_requirement

Release historydanger

The package has 16 releases and a history of regular releases, but its latest release was in March 2016 and it has had no releases in the last 12 months. That long release gap materially raises abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates that maintenance is currently dormant.

Repo popularitycaution

The repository has only 1 star and 1 fork, providing little community evidence to offset the lack of recent maintenance. Popularity is supporting evidence rather than a standalone health verdict.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This does not show a vulnerability, but it leaves the process for reporting and handling security issues unclear.