blomstra/oauth-slack

It has a clear README, MIT licensing, focused runtime dependencies, and organization backing. The unpinned workflow actions and absent security policy add hygiene concerns, while the available release documentation does not offset the weak maintenance evidence.

Latest 0.1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, and the latest was published in November 2022; there have been no releases in about 3 years and 10 months. This is strong evidence of abandonment risk for a package intended as an application extension.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. No provided activity signal compensates for this lack of recent maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a modest process gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, especially for an extension handling OAuth credentials.

Workflow audit

The single workflow was fully analyzed with no untrusted checkout or script-injection findings, but all 3 action references are unpinned. That leaves build inputs less reproducible and increases workflow supply-chain exposure.