prompts

Build provenancecaution

No build attestation, trusted publisher, or staged publishing provenance is available, leaving the publication path less transparent. This is a supply-chain transparency gap rather than evidence that the package is unsafe.

Project backingcaution

The repository is owned by an individual account rather than an organization, so the project has a relatively narrow visible ownership base. This is partly offset by the repository's established history and popularity.

Release historycaution

The package has 36 releases since February 2018, but none in the last 12 months and its latest registry release was in October 2021—nearly five years ago at collection time. The long release gap lowers confidence in current maintenance.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. Although the repository was pushed in May 2025, the recent absence of commits raises abandonment and responsiveness concerns.

Repo issue activitycaution

The repository has 115 open issues and 37 open pull requests, with no issues or pull requests closed in the last month and only two new pull requests. This indicates a backlog and limited recent throughput.