performance-now

Release historydanger

The package has 11 releases but none in the last 12 months, with the latest release in February 2017—about 9 years ago—indicating long-term maintenance inactivity.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, reinforcing the release-history evidence of abandonment risk.

Build provenancecaution

No build attestation, trusted publisher, or staged publishing is present, so consumers have limited evidence connecting the artifact to its source.

Lifecycle scriptscaution

A prepublish lifecycle script adds some supply-chain and reproducibility risk because package behavior can depend on publishing-time execution.

Maintainerscaution

Only one registry account has publish access, leaving a thin publishing base; this is a concern, though the project is also small and has no runtime dependencies.