event-source-polyfill

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this is strong evidence of stalled maintenance.

Build provenancecaution

The release has no build attestation or trusted-publisher provenance. This is a transparency limitation, but it is not by itself evidence that the release is unsafe or abandoned.

Release historycaution

The package has 40 releases and a long history, but it has had no releases in the last 12 months; the latest release was published in August 2022. This materially lowers confidence in active maintenance.

Repo issue activitycaution

The repository has 41 open issues and two open pull requests, but no issues or pull requests were opened or closed in the last month. The unresolved queue and inactivity add maintenance concern.

Repo toolingcaution

The repository uses build tooling including Grunt, webpack, and npm scripts, which supports a structured project. It has no security-scanning tools, leaving a modest maintenance-hygiene gap.