This is a small JavaScript utility that checks whether a given value is a JS Map. It’s designed to work across realms and iframes, which makes it useful when validating Map values in different execution contexts.
Project status
- The source appears quiet, with the most recent published update tag seen in the provided history at v2.0.3 (2024-03-08). Although there was an upstream push on 2025-12-30, the available data does not show additional tagged updates after 2024-03-08, so active maintenance is not clearly evidenced.
- Update cadence looks irregular, with very large gaps between updates (for example, v2.0.2 in 2020, then v2.0.3 in 2024). This suggests an overall “maintenance when needed” pattern rather than steady iteration.
AI summary generated
Recent updates
v2.0.3
No release notes were provided for v2.0.3. The code diff shows runtime logic in index.js is effectively unchanged, while the release primarily adds TypeScript typings and updates build/publishing configuration (scripts, npmignore generation, and metadata like sideEffects).
Featuresv2.0.2
This release (v2.0.2) has no publisher-provided release notes. The actual diff is almost entirely build and development infrastructure, including new GitHub Actions workflows, updated npm scripts for testing with coverage, and a set of devDependency version bumps.
v2.0.1
Release v2.0.1 was published on 2019-12-17, but no release notes were provided by the publisher. As a result, there is no documented information about new features, bug fixes, breaking changes, security updates, or migration steps in the available data.
v2.0.0
Release v2.0.0 was published on 2019-11-12, but no release notes were provided, so the changes in this version are not described. As a result, developer-impacting items like breaking changes, new features, bug fixes, security updates, or dependency changes cannot be determined from the provided data.
v1.0.1
This is a small maintenance release (v1.0.1) with primarily repository and documentation changes. The core runtime logic in index.js appears unchanged, but the project’s test setup and contributor workflow were modified.
v1.0.0
This release is tagged v1.0.0, but the publisher did not provide any release notes. As a result, there is no documented information about new features, fixes, breaking changes, security, or migration requirements.