wuqian99/blog

Its small source tree, MIT license, and lack of install-time scripts keep the package straightforward to inspect. The project has seen no new release or repository push for over six years, leaving maintenance and compatibility uncertain.

Latest 0.0.1

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published over six years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, although the package may be intentionally minimal.

Package file tree

The package contains only seven files, including a README, manifest, and one source file. This is consistent with a tiny package but provides little evidence of maturity or maintenance depth.

Project backing

The repository is owned by an individual user rather than an organization, so the single registry maintainer does not have broader organizational backing to compensate for the limited maintenance evidence.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external indication of active use or community support.

Repo tooling

Composer is used for the build, but no security scanning tool is configured. For a very small package this is a modest transparency gap rather than a severe risk.