reed-jones/neocities

The repository has no security policy and no recent commit activity, leaving limited evidence of ongoing maintenance. Clear licensing, release notes, a usable README, and a very small dependency surface reduce adoption friction.

Latest v0.2.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was about six years ago, with no releases in the past year and only three releases overall. This is strong evidence of a largely inactive release process.

Repo commit activity

There were no commits and no active maintainers in the past three months. Combined with the last registry release being about six years ago, this indicates weak current maintenance.

Repo tooling

Composer is used for the build, but no security-scanning tools are reported. The missing scanning is a maintenance hygiene gap rather than evidence that the package cannot be built.

Security policy

The repository has no security policy. For a client library that handles API credentials, this reduces transparency about how vulnerabilities should be reported and managed.

Version stability

Version v0.2.1 is not a prerelease, which avoids prerelease instability, but it remains below a stable major version and has not advanced since the old release history.