danielstjules/sliceable-stringy

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in May 2017. This indicates roughly nine years of inactivity and materially raises maintenance risk.

Release historycaution

The package has only two releases, both from February 2014, with no releases in the last 12 months. That long period without a new release is a meaningful abandonment concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. This is a modest hygiene gap and not evidence that the package is unsafe by itself.

Repository archivedcaution

The repository is not archived, which is a compensating sign, but its last push was still about nine years ago. The non-archived status does not offset the observed lack of recent work.

Security policycaution

The repository has no security policy. For a small, old library this is a transparency gap, though it is secondary to the much stronger inactivity concerns.