sands/asasi-http

There is no security policy or automated security scanning, and the repository shows no meaningful community activity. Organization ownership and a clear MIT license provide some accountability, but they do not offset the age and limited project evidence.

Latest 0.2

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in January 2017, with no release in more than nine years. This is strong evidence of abandonment risk for a library dependency.

Package file tree

The package and repository each contain only seven files, consisting mainly of two source files and basic metadata. This small footprint is not inherently unsafe, but it provides little evidence of testing, documentation, or maintained project practices.

Package scaffolding

The artifact includes a README, but it is only 16 characters long and the package and repository contain no tests or changelog. Missing tests and changelog are normal for published artifacts, but the minimal consumer documentation is a genuine gap for a library.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. With the repository last pushed in 2017, the absence of activity supports the broader abandonment concern.

Repo popularity

The repository has zero stars and forks, with four watchers. Popularity is only supporting evidence, but these figures provide no independent indication of an active user or contributor community.