css.escape

Build provenancecaution

No build attestation or trusted-publisher provenance is available, which limits publication transparency. This is a caution rather than a severe health issue because the package is a small, directly shipped JavaScript file with no runtime dependencies.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing shown. That makes the inactive commit history more dependent on a single maintainer.

Release historycaution

The package has 10 releases and a historically regular median interval of about 49 days, but no release has been published in about 10 years. That long release gap materially lowers confidence in ongoing maintenance, even for a stable polyfill.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last 3 months. Combined with the old latest release, this is the main abandonment concern, though the package's narrow and mature scope partly compensates.

Repo issue activitycaution

There are 4 open issues and 1 open pull request, but no issues or pull requests were opened or closed in the last month. This supports the conclusion that active maintenance is currently limited.