linio/safeecho

The MIT license, tests, small dependency set, and organization-backed repository support straightforward adoption. No security scanning or security policy is provided, increasing the maintenance and review burden.

Latest 0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about eight years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance, although the repository remains available and unarchived.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with repository activity having stopped about five years ago. This materially raises the risk of unaddressed compatibility issues.

Repo popularity

The repository has only 1 star and 1 fork, indicating limited adoption and external validation. Popularity is supporting evidence rather than a verdict, so this is a modest concern.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. For a small library this is a hygiene gap rather than a standalone severe risk.

Security policy

No repository security policy was found, leaving no documented process for reporting or handling vulnerabilities. This adds transparency and maintenance risk.