@babel/plugin-proposal-class-static-block

Registry deprecationdanger

NPM marks the package deprecated at package scope because the proposal merged into the ECMAScript standard and directs users to @babel/plugin-transform-class-static-block. This makes the release unfit for a new dependency despite the active project behind it.

Release historydanger

The package has had no releases in more than three years, with zero releases in the last 12 months. That is consistent with the package being superseded rather than actively maintained.

Repo package mentioncaution

The linked repository name does not match the package and its README does not mention the package, which is a caution under the package-ownership check. The Babel organization backing and monorepo structure partly explain the mismatch but do not remove the signal entirely.

Workflow auditcaution

The audit analyzed all 13 workflows and found no untrusted checkout or script-injection sink, but 119 of 120 action references are unpinned. High-confidence template-injection findings are hygiene concerns here, while the trusted-publishing finding warrants additional caution.