neo/little-sail

The package is clearly identified, MIT-licensed, and includes useful documentation, a changelog, and release notes. Its small dependency surface and lack of install scripts reduce adoption friction, but the absent security policy leaves maintenance practices less transparent.

Latest v1.0.6

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release for about four years, with zero releases in the last 12 months. This is meaningful abandonment risk despite a previously regular release interval.

Repo commit activity

There were no commits and no active maintainers in the last three months, reinforcing that the project is not currently maintained.

Repo issue activity

There was no issue or pull-request activity in the last month, with one issue still open. This is consistent with a quiet project but is weaker evidence than the prolonged release gap.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. Build support is positive, while the missing scanning is a modest hygiene concern.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled. The lack of security scanning also leaves this gap uncompensated.