semver-try-require

micro module to require or import (versions of) modules that might not be there

semver-try-require@7.0.0 was published on 2024-05-04. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^18.17||>=20.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All semver-try-require versions · Permanent reference to 7.0.0

Package specifications

Version7.0.0
License declarationMIT
Published2024-05-04T10:55:40.116Z
Node.js requirement^18.17||>=20
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size8.70 KiB
Published file count7
Package typecommonjs
ES module entryNot declared
Default entrydist/try-require.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars3
Repository forks3

Install semver-try-require 7.0.0

npm install semver-try-require@7.0.0
pnpm add semver-try-require@7.0.0
yarn add semver-try-require@7.0.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — project is archived
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 0/26 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness