inspirum/balikobot

This is a generally credible and mature package: it has been released since 2018, has 64 releases, a stable non-prerelease version, an active unarchived organization-backed repository, clear MIT licensing, documented source structure, repository tests, and no install-time lifecycle scripts. The main concern is maintenance continuity: although the release was published recently and the repository was recently pushed, there were no commits or active maintainers in the preceding three months. Missing repository security policy and undeclared workflow token permissions are additional transparency and CI-hardening gaps, but the analyzed workflow showed no dangerous checkout, trigger, or script-injection patterns.

Latest v7.16.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a modest single-publisher continuity risk; this is partly offset by the linked repository being owned by an organization.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months. Despite the recent release and repository push, this is a meaningful indication of currently thin maintenance activity.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull-request activity. The clean queue is positive, but the lack of activity provides little evidence of active community maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected, leaving a security-process gap.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and coordinated disclosure.