esm-resolve

Build provenancecaution

The release has no build attestation or trusted-publisher provenance, limiting transparency about how the artifact was produced.

Maintainerscaution

Only one registry maintainer is listed, so publishing continuity depends on a single person; the user-owned repository provides no broader organizational backing.

Release historycaution

The package has had no release in over two years and no releases in the last 12 months, which is a meaningful maintenance concern despite its 12-release history.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Repo toolingcaution

The project uses TypeScript and esbuild, but no security scanning tooling is reported, leaving a modest maintenance-hygiene gap.