n4s 5.0.6

Assertion library for form validations

n4s@5.0.6 was published on 2023-09-25. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All n4s versions · Permanent reference to 5.0.6 · View npm registry JSON · Latest release

Package specifications

Version5.0.6
License declarationMIT
Published2023-09-25T22:49:59.740Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size562.68 KiB
Published file count118
Package typeNot declared
ES module entry./dist/es/n4s.production.js
Default entry./dist/cjs/n4s.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars2669
Repository forks97

Install n4s 5.0.6

npm install n4s@5.0.6
pnpm add n4s@5.0.6
yarn add n4s@5.0.6

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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.

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

Evidence and freshness