invoice/block-chain-data

The package is small and clearly documented, with a matching repository and a license file identifying MIT. Composer build support is present, but the project has no security scanning or security policy.

Latest 1.1

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in June 2019, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as an application dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2019.

Repo popularity

The repository has only 2 stars, 1 fork, and 1 watcher. Low popularity is supporting evidence rather than decisive, but it provides little community backing to offset the inactivity.

Repo tooling

Composer is used for the build, which supports reproducible package handling, but no security scanning tools are configured. The missing scanning reduces maintenance assurance without proving a defect.

Security policy

The repository has no security policy. This is a transparency and maintenance gap, although it is less severe for this very small package than for a security-sensitive framework.