is-symbol is a small JavaScript utility that answers the question, “Is this an ES6 Symbol value?”. It can be used in Node.js or other JS code to test whether a given input is a Symbol, including cases like Symbol.iterator and Symbol.for.
Project status
- The source appears to be in a low-activity maintenance state, with the latest published updates dated 2024-12-13 (v1.1.1) and no further versioned updates shown since then, despite an upstream push on 2026-03-16.
- The apparent update cadence is sporadic rather than regular, with updates in 2015, 2018 to 2021, and again in late 2024, and a long gap from 2024-12 to today (2026-06-09).
AI summary generated
Recent updates
v1.1.1
v1.1.1 updates the internal implementation to use the `call-bound` package directly instead of `call-bind/callBound`. It also bumps runtime dependency versions (`call-bound`, `has-symbols`, `safe-regex-test`) and adjusts CI workflow job definitions.
v1.1.0
v1.1.0 contains a refactor of the isSymbol implementation to use call-bind and safe-regex-test, plus the addition of TypeScript typings. No release notes were provided by the publisher in the release_notes section, so the documented change list is effectively empty.
Featuresv1.0.4
Release v1.0.4 was published on 2021-05-08, but no release notes were provided by the publisher. Because the release description contains no change details, it is not possible to determine whether this upgrade includes new features, breaking changes, bug fixes, security updates, or dependency updates.
v1.0.3
Release v1.0.3 does not include any publisher-provided release notes. The code diff shows the primary changes are to development tooling and CI configuration, plus dependency bumps (notably has-symbols). No runtime library source changes are present in the provided diff.
Securityv1.0.2
v1.0.2 refactors the is-symbol implementation to delegate Symbol capability detection to the has-symbols package and updates tests to use object-inspect for safer debug output. The published GitHub release notes field is empty, so consumer-visible behavior changes must be inferred from the code diff.
v1.0.1
Release v1.0.1 makes only metadata updates. It bumps the package version and updates the description text, and the changelog entry reflects a corrected description.
v1.0.0
Release v1.0.0 was published, but no release notes were provided by the publisher, so no documented behavior changes, API updates, or migration guidance are available from the release description. To assess upgrade impact, you will need to compare this tag against the previous version in the repository (code diff) and review changelogs or commit history.