litto/uploader

Its small scope, clear README, release notes, and single runtime dependency make the package straightforward to inspect. However, the project has had no release or commit activity for over four years, and its license metadata conflicts with the MIT license file.

Latest v1.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over four years ago, with no releases in the last 12 months. That is strong evidence of stagnation for a dependency that may need fixes or compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

License

The artifact contains an MIT license file, so the release is licensed, but the manifest declares it as proprietary. That unresolved mismatch creates avoidable legal and transparency uncertainty.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. This is a modest hygiene gap rather than evidence that the release is unsafe.

Security policy

The linked repository has no security policy. For a file-upload library, the absence of a documented vulnerability-reporting path is a meaningful maintenance gap.