Back to Explore

inspect-js/has-symbols

GitHub
2 watchersOpen source

Last release:

Checks whether a JavaScript environment supports ES6 Symbol, returning true when native Symbols are available. It also provides a shams-based check (for example via `has-symbols/shams`) to detect Symbol shims that mostly follow the spec.

Project status

  • The source appears to be maintained, with an upstream push on 2026-04-29, but the last published package update in the provided history is v1.1.0 on 2024-12-02, suggesting active repo activity with less frequent package updates.
  • Update cadence looks relatively slow, about yearly or longer between versioned updates (notably 2024-12-02, then earlier 2022-03-01, 2021-02-27, 2019-11-17).

AI summary generated

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

Recent updates

  • v1.1.0

    v1.1.0 bumps the package version and introduces new TypeScript declaration files for the main export and the shams helper. It also updates npm publishing behavior (auto-generated npmignore via a prepack step) and modernizes CI workflows and GitHub Actions dependencies. Runtime code changes appear to be limited to type-related casts and small syntax adjustments, but packaging and TypeScript surface area can still affect consumers.

    SecurityFeatures

  • v1.0.3

    v1.0.3 appears to be a packaging and CI-focused release, with no runtime source code changes shown in the provided diff. The main documented artifacts in the code diff are GitHub Actions workflow updates, package.json metadata and npm lifecycle script adjustments, and devDependency version bumps.

  • v1.0.2

    Release v1.0.2 was published on 2021-02-27, but no release notes were provided by the publisher. As a result, the changes in this version cannot be determined from the release information alone.

  • v1.0.1

    v1.0.1 does not include any release-note content. The diff shows this release is primarily repository and tooling maintenance (CI config, changelog automation, auditing command changes, and dev dependency updates), with no clear runtime/library behavior changes.

    SecurityFeatures

  • v1.0.0

    This release is tagged v1.0.0, but no release notes were provided. As a result, the changes included in this version, potential breaking changes, and any migrations cannot be determined from the published information.