davedevelopment/stiphle

Maintainerscaution

The registry lists one maintainer. That is a narrow publishing base, and the absence of recent repository activity provides no compensating evidence of active maintenance.

Release historycaution

The latest release was nearly four years ago, with no releases in the past year and a long median release interval. This suggests limited ongoing maintenance, though the package has an established release history.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long gap since the latest release. This is meaningful abandonment risk for a dependency.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This modestly reduces evidence of ongoing security hygiene.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, although it does not by itself indicate unsafe code.