papi-ai/ingest

Usable with caveats: the package is clearly backed, tested, licensed, and actively released, but it is only 51 days old with two releases and all recent commits from one contributor. Missing security policy and unspecified workflow token permissions add transparency concerns.

Latest v0.15.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is very new at 51 days old and has only two releases, so there is limited evidence of long-term maintenance or release stability.

Repo bus factor

All recent commits come from one contributor, creating concentration risk. Organization ownership provides some ability to hand maintenance to another person, but no second active contributor is shown.

Repo commit activity

There were two commits in the last three months, all from one active maintainer. This shows recent work but provides only limited evidence of sustained maintenance capacity.

Repo popularity

The repository has no stars, forks, or watchers. This is weak supporting evidence given the package is only 51 days old, so it does not independently establish a health problem.

Repo tooling

The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence that the package is unsafe.