optimize-css-assets-webpack-plugin

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old release history, this indicates that maintenance has effectively stalled.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, reducing publication transparency. This is a supply-chain transparency gap, but it is not by itself evidence that the release is unsafe.

Maintainerscaution

Only one registry account has publish access. That is a modest continuity risk for an individually owned project, though registry access alone does not establish whether the person is actively maintaining it.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the thin maintainer base or inactive development.

Release historycaution

The package has 27 releases and a historically regular median interval of about 26 days, but its latest release was over five years ago and there were no releases in the last 12 months. This is a substantial maintenance concern.