jplambert/phrrs

Release historydanger

The package has only two releases, both published about 10 years ago, with none in the last 12 months. This is strong evidence of abandonment for a dependency that may need ongoing compatibility or security fixes.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and indicating no visible current maintenance.

Licensecaution

No declared license, license file, or repository license file was detected. This creates a material adoption and redistribution risk for an open-source dependency.

Project backingcaution

The repository is owned by an individual rather than an organization, so the small maintainer footprint is not explained by organization-backed publishing. Combined with inactivity, this increases abandonment concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a minor transparency gap, especially alongside the long period without maintenance.