loglevel-plugin-prefix

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the strongest maintenance concern.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, reducing publication transparency. This is a transparency gap rather than evidence that the release is unsafe.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although the linked repository is directly owned by the same individual.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the single-maintainer continuity risk.

Release historycaution

The package has 15 releases but none in the last 12 months, and its latest release was over eight years ago. That long release gap is a meaningful abandonment concern despite the package's earlier release history.