@bcoe/v8-coverage

Build provenancecaution

No build attestation or trusted-publisher provenance is reported, reducing release transparency, but this is a transparency gap rather than evidence that the package is unsafe.

Maintainerscaution

Only one registry account has publish access. This is a limited publishing base and increases continuity risk, though access records do not prove actual maintenance activity.

Release historycaution

The package has 8 releases over about 7 years, but none in the last 12 months; the latest release was about 20 months ago, indicating slowed maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last 3 months, reinforcing the concern that maintenance has stalled.

Repo toolingcaution

No build tool or security scanning tool is reported, leaving fewer automated checks around future changes and releases.