Back to Explore

inspect-js/is-finalizationregistry

GitHub
2 watchersOpen source

Last release:

This JavaScript module checks whether a given value is a JS FinalizationRegistry, with support for cross-realm usage like iframes. It is useful for runtime type checking of FinalizationRegistry instances.

Project status

  • Maintenance status: The last upstream push was 2024-12-17, which is well over 1 year ago relative to 2026-06-09, so the source appears quiet/dormant rather than actively maintained.
  • Update cadence: Updates were sporadic early on (2020, 2021), then resumed with small increments in 2024 (v1.1.0 on 2024-11-23, v1.1.1 on 2024-12-17), with no evidence of continued updates since.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.1.1

    Release v1.1.1 does not include publisher-provided release notes. The code changes are primarily internal refactoring (switching from `call-bind` to `call-bound`), plus package metadata and CI matrix tweaks.

  • v1.1.0

    Release v1.1.0 includes TypeScript type definitions and multiple repository and tooling updates (CI workflows, build/publish scripting, lint/test scripts). The release notes section is empty, so this analysis relies on the actual code and manifest diffs. The runtime change is in how the module probes FinalizationRegistry via `register`.

    BreakingFeatures
  • v1.0.2

    Release v1.0.2 was published on 2021-10-06, but no release notes were provided by the publisher. As a result, there is no documented information about new features, bug fixes, breaking changes, or security updates in this release.

  • v1.0.1

    This release (v1.0.1) primarily migrates CI from Travis to GitHub Actions and adds code coverage instrumentation via nyc. Runtime-facing changes appear minimal, with the main package-level change being an added subpath export for package.json.

  • v1.0.0

    This release is tagged v1.0.0, but the publisher did not provide release notes. As a result, there is not enough documented information to determine new features, breaking changes, bug fixes, security updates, or migration requirements.