nivseb/strict-request

Project backingcaution

The package and repository are owned by the same individual account, so ownership is coherent, but there is no organization backing shown to compensate for a thin maintainer base.

Release historycaution

This is the package's only release, published 475 days after collection with no releases in the last 12 months, so ongoing maintenance is unproven.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months, which is consistent with the package's single-release history and weakens evidence of active maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; the repository's security policy provides some compensating transparency.

Workflow auditcaution

Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, or audit findings. However, all four action references are unpinned, leaving avoidable supply-chain exposure in the build workflows.