@babel/regjsgen

Release historydanger

Only one release exists, published about three years and eight months ago, with no releases in the last 12 months. This limits evidence of ongoing release maintenance.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less transparent. The package is nevertheless a small, directly shipped JavaScript artifact.

Project backingcaution

The registry uses the @babel namespace, but the linked repository is owned by an individual account rather than an organization. The separate backing context makes long-term stewardship less clear.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Recent pull-request activity partly offsets this, but direct maintenance evidence remains thin.

Repo toolingcaution

The repository reports no build tools or security scanning tools. For a small single-file JavaScript package this is a hygiene gap, but not a severe dependency risk.