paysera/lib-lock-bundle

Clear documentation, tests, changelog, and organization backing support adoption. The repository has had no commits or releases for about 18 months, and its three workflow actions are unpinned, leaving maintenance and build-integrity concerns.

Latest 2.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, while the latest push was about 18 months ago. This materially raises maintenance and abandonment risk.

Release history

The package has existed for about 8 years with 11 releases and a roughly 51-day median release interval, but it has had no release in the last 12 months; the latest release was about 18 months ago.

Repo issue activity

There are no open issues and one open pull request, with no issue or pull-request activity in the last month; this is consistent with a quiet project but is not severe on its own.

Repo popularity

The repository has no stars and only eight forks, indicating limited adoption evidence. Popularity is supporting evidence rather than a health verdict, and the project has organization backing and a coherent package.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than evidence of unsafe code.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
symfony/lock Version ^v3.4 \|\| ^4.4 \|\| ^5.4 \|\| ^6.0	—	—
symfony/yaml Version ^4.0 \|\| ^5.0 \|\| ^6.0 \|\| ^7.0	—	—
symfony/config Version ^3.0 \|\| ^4.0 \|\| ^5.0 \|\| ^6.0	—	—
symfony/console Version ^4.4 \|\| ^5.3 \|\| ^6.0	—	—
symfony/http-kernel Version ^3.0 \|\| ^4.0 \|\| ^5.0 \|\| ^6.0	—	—