@webcontainer/env

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. This is a direct sign of currently stalled development and materially increases abandonment risk.

Build provenancecaution

The release has no build attestation or trusted-publisher provenance. This limits publication transparency, although it is a supply-chain hygiene gap rather than evidence that the package is unsafe.

Release historycaution

The package has only four releases since May 2022, with the latest on March 28, 2024 and no releases in the following roughly two years and six months. This weakens confidence that fixes and compatibility updates are still arriving.

Repo issue activitycaution

The repository has 815 open issues, received 17 new issues in the last month, and closed only one, with no pull requests merged. That backlog and imbalance raise concerns about responsiveness.

Repo package mentioncaution

The repository name does not match the package and its README does not mention @webcontainer/env, so the package-to-repository linkage is not transparent. Organization backing helps, but does not fully remove that concern.