@jimp/plugin-cover

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, a concrete sign of slowed maintenance despite the recent package release.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable.

Release historycaution

The package has existed for about 8 years with 243 releases, but only one release in the last 12 months indicates a currently slow cadence.

Repo issue activitycaution

There were two new pull requests but no merged pull requests and no closed issues in the last month, suggesting limited recent throughput.

Repo package mentioncaution

The repository name does not match this package and its README does not mention the package, creating a package-to-source transparency concern; the name mismatch alone would be ordinary for a monorepo, but the missing README mention adds caution.