b13/slash-force

Release historycaution

The package is mature at about 2 years and 10 months old, but has only five releases and one release in the last 12 months, with roughly 8-month typical gaps. The recent 1.2.0 release provides some evidence of continued care, but cadence remains sparse.

Repo bus factorcaution

All recent commits came from one contributor, creating concentrated maintenance responsibility. Organization backing provides some ability to hand off maintenance, but no second active contributor is shown in this period.

Repo commit activitycaution

Only one commit from one active maintainer was recorded in the last three months. The recent activity is positive, but the very low volume provides limited evidence of sustained maintenance.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling was detected. For a small package this is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency, although the absence alone does not indicate that the release is unsafe.