flagupdown/scanner

The MIT license, focused file layout, README, and minimal dependency set make the package straightforward to inspect and integrate. Its lack of tests and security policy leaves little support for maintaining or evaluating future changes.

Latest v0.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about 7 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency whose compatibility may need ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the last push being about 7 years ago, this indicates sustained inactivity rather than a short pause.

Project backing

The repository is owned by an individual account rather than an organization. This does not imply poor health, but it provides no organizational backing to offset the lack of recent activity.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a dormant project, although the absence of issues is not itself evidence of poor code quality.

Repo popularity

The repository has zero stars, forks, and watchers, providing no supporting evidence of an active user or contributor community. Low popularity alone is not disqualifying, but it offers no compensation for the inactivity.