is-equal-shallow

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the last push being more than 8 years ago. This is the main reason to treat the package as maintenance-stale.

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This lowers publication transparency, but it is a supply-chain transparency gap rather than evidence that the package is unfit to use.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the thin maintenance evidence.

Release historycaution

There were four releases, but the latest was published in June 2015 and there have been no releases in the last 12 months. This is a meaningful maintenance concern for a dependency, although the package is small and has a stable published version.

Repo issue activitycaution

There is one open issue and one open pull request, but no new or closed issues or pull requests in the last month. This suggests little current project activity.