lablnet/input

Release historydanger

This package has only one release, published over seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment, although the release is stable rather than experimental.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no updates for over seven years.

Project backingcaution

The repository is owned by a user account rather than an organization, so there is no observed organizational backing to compensate for the long maintenance gap.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. The missing scanning is a hygiene gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, so consumers have no documented channel or process for reporting vulnerabilities. This weakens transparency for a package that processes HTTP input.