net-tools/ui

The MIT license, matching repository, stable versioning, and recent release cadence support adoption. The single registry maintainer, absent security scanning and policy, and inactive recent commit window leave meaningful maintenance and transparency concerns.

Latest 1.6.6

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access. That is a limited publishing base and increases continuity risk if the maintainer becomes unavailable.

Package scaffolding

The artifact contains no README, tests, or changelog, while the repository also reports no tests or changelog. For a small compiled-style CSS and JavaScript asset package, missing artifact tests and changelog are expected, but the lack of repository tests limits maintenance evidence.

Project backing

The package and repository share the net-tools namespace, but the repository owner is an individual user rather than an organization. This provides a matching source identity without organizational continuity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This conflicts with the strong release cadence and leaves current source maintenance uncertain.

Repo issue activity

There are no open issues or pull requests, and no issue or pull-request activity in the last month. This is neutral for a small stable package but offers little evidence of an active community.