This module checks whether a value is a JavaScript Number object, including boxed numbers like new Number(42). It is designed to work across different realms or iframes, which can be useful for type checks in browser or mixed-window environments.
Project status
- Maintenance status: Not clearly “actively maintained” as of today, because the most recent published updates appear to be v1.1.1 on 2024-12-16, with the latest recorded upstream push on 2025-12-30 but no corresponding new published update shown in the provided summaries.
- Update cadence: Releases are infrequent, with noticeable gaps (for example, 2015 to 2021, then 2022, then 2024), suggesting a low-frequency maintenance pattern rather than continuous development.
AI summary generated
Recent updates
v1.1.1
Release v1.1.1 makes a small internal refactor in index.js to use `call-bound` directly instead of importing `callBound` from `call-bind/callBound`. It also updates the dependency set (including replacing `call-bind` with `call-bound`) and bumps some dev dependency versions. No publisher release notes were provided, so changes are inferred from the actual diff.
v1.1.0
Release v1.1.0 introduces TypeScript typings and refactors the core implementation to use call-bound intrinsics via call-bind. It also updates internal tooling and CI workflows (node test matrix split) and changes npm packaging behavior by introducing an auto-generated .npmignore step. No release notes were provided by the publisher for this version.
Featuresv1.0.7
Release v1.0.7 was published on 2022-04-02, but no release notes were provided by the publisher. As a result, there is no documented information here about new features, breaking changes, bug fixes, security updates, performance improvements, or migration steps.
v1.0.6
v1.0.6 makes `is-number-object` determine `@@toStringTag` support via the `has-tostringtag` shim helper instead of directly probing `Symbol.toStringTag`. The release notes provided by the publisher are missing, but the code changes indicate a runtime behavior adjustment to better handle symbol shams. The repo also adds a Core-JS loaded test harness and updates CI to run it.
v1.0.5
This release (v1.0.5) contains mostly build and test infrastructure changes (GitHub Actions workflows, nyc coverage setup, and npm publish script lifecycle updates). The only runtime code change is in the number-object detection logic related to how `Symbol.toStringTag` is feature-detected. Release notes were not provided, so the behavioral intent of the runtime change is not documented there.
v1.0.4
v1.0.4 makes largely internal changes, focusing on test/CI tooling, linting configuration, and repository automation (auto-changelog, funding, workflows). The runtime export in index.js appears effectively unchanged, with modifications limited to code formatting, while tests and development scripts were updated substantially.
Securityv1.0.3
Release v1.0.3 updates the core number-object detection logic. Specifically, it adds a fallback behavior for environments that do not support Symbol.toStringTag, and bumps the package version.
v1.0.2
No publisher release notes were provided for v1.0.2. The included CHANGELOG entry indicates a package.json fix and a micro-optimization to reduce the amount of code executed inside a try/catch.
v1.0.1
Release v1.0.1 adds fast-path checks to the main `isNumberObject` predicate, and updates tests to use `Object(42)` for the boxed-number case. No publisher release notes were provided, so the practical behavior change is only visible in the code diff and changelog update.
Breakingv1.0.0
This release is tagged v1.0.0, but the publisher did not provide any release notes. As a result, there is no described information about new functionality, bug fixes, security updates, or potential breaking changes in this update.