jacobemerick/archangel

It has tests, release notes for this version, a clear MIT license, and a small dependency surface. The repository has no security policy or security scanning, leaving limited evidence of ongoing security maintenance.

Latest 2.1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in over 10 years, with all four releases concentrated in January and February 2016. That long gap is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release hiatus and indicating no current maintenance capacity.

Repo popularity

One star, zero forks, and one watcher provide little community evidence to offset the lack of recent maintenance, though popularity is supporting evidence rather than decisive on its own.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is a modest positive, while the missing security checks reduce maintenance transparency.

Security policy

The repository has no security policy, so users have no documented process for reporting vulnerabilities or understanding security support. This is a transparency gap, amplified by the absence of recent activity.