mixme

Build provenancecaution

The release has no build attestation or trusted-publisher metadata, so consumers cannot verify its build origin through registry provenance. This is a transparency gap, but not evidence that the package is unsafe.

Release historycaution

The package has existed for 3098 days and has 24 releases, but it has had no release in the last 12 months despite a latest release in February 2025. This indicates a meaningful slowdown in maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. That is the clearest evidence of currently slowed development, though the repository is not archived.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, although one issue and three open pull requests remain. This is a modest sign of limited current maintenance.

Repo toolingcaution

The project uses TypeScript, tsup, and npm scripts, and the repository has a structured build setup. It has no security scanning tooling, leaving automated security coverage unclear.