state-local

Release historydanger

The package has had no registry release in more than five years, with zero releases in the last 12 months. Its eight-release history shows an established package, but the long publishing gap lowers confidence in ongoing maintenance.

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This limits release transparency, though it is not by itself evidence that the package is unsafe to depend on.

Maintainerscaution

Only one registry account has publish access, and the repository is owned by that same individual rather than an organization. This leaves limited publishing and maintenance redundancy.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, indicating no current development activity. The repository is not archived, but that does not offset the present inactivity.

Repo toolingcaution

The repository uses a build toolchain including Rollup, npm scripts, and Babel, but no security scanning tools were detected. The missing scanning is a modest transparency and oversight gap.