ts-custom-error

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving the artifact's build origin less transparent. This is a supply-chain transparency gap, not evidence of maliciousness.

Maintainerscaution

Only one registry maintainer is listed. With a user-owned rather than organization-backed repository, this represents a meaningful bus-factor and continuity concern.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the single-maintainer concern.

Release historycaution

The package has existed since March 2018 with 14 releases, but its latest release was November 1, 2022 and it had no releases in the last 12 months. This materially lowers confidence in ongoing maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the absence of registry releases since November 2022, this is a clear abandonment concern.