@adraffy/ens-normalize

Release historycaution

The package has existed for 1,761 days with 52 releases, but only one release in the last 12 months despite a median historical interval of about 5 days. The recent repository push partly offsets this slowdown, but the registry cadence warrants caution.

Repo bus factorcaution

All 4 recent commits came from one contributor, so maintenance depends heavily on a single person. The active repository and recent release documentation provide some compensation but do not remove the continuity risk.

Repo toolingcaution

The project uses Rollup and npm scripts, showing an established build process, but no security scanning tools were detected. This is a modest transparency and assurance gap rather than a severe concern.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a hygiene gap for a package handling name normalization, but it is not evidence of abandonment by itself.