@stdlib/assert-is-regexp-string 0.1.1

Test if a value is a regular expression string.

@stdlib/assert-is-regexp-string@0.1.1 was published on 2023-10-04. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=0.10.0.

All @stdlib/assert-is-regexp-string versions · Permanent reference to 0.1.1 · Latest release

Package specifications

Version0.1.1
License declarationApache-2.0
Published2023-10-04T00:04:19.185Z
Node.js requirement>=0.10.0
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size26.33 KiB
Published file count11
Package typeNot declared
ES module entryNot declared
Default entry./lib
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository stars2
Repository forks0

Install @stdlib/assert-is-regexp-string 0.1.1

npm install @stdlib/assert-is-regexp-string@0.1.1
pnpm add @stdlib/assert-is-regexp-string@0.1.1
yarn add @stdlib/assert-is-regexp-string@0.1.1

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.

Security-Policy9/10 — security policy file detected
Maintained2/10 — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST0/10 — no SAST tool detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4

Evidence and freshness