selfworks/recurr

Release historydanger

The package has 58 releases but none in about eight years, indicating prolonged release inactivity and increasing abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, reinforcing the prolonged inactivity seen in the release history.

Licensecaution

An MIT declaration and license file provide clear licensing, but the artifact also identifies BSD-3-Clause text that the declaration does not cover, creating a minor licensing-transparency concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected; this is a modest transparency and maintenance-hygiene gap rather than a severe risk.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear for a library that may remain in production use.