Beispiel

Generate non-cryptographic identifiers with nanoid/non-secure and verify silent empty-string returns on negative size inputs versus cryptographic RangeError

sha256:33fa894d2e8aaa8166a9bf954a74dc0f162cef7ee04cb938033b25c057f076c8

Fall

Ziel

Generate non-cryptographic identifiers with nanoid/non-secure and verify silent empty-string returns on negative size inputs versus cryptographic RangeError HOW

Pakete

nanoid 6.0.1

Umgebung

node

Erstellt

2026-08-17T19:54:26Z

Häufige Annahme

Negative size arguments passed to nanoid/non-secure functions are expected to throw a RangeError matching cryptographic nanoid behavior.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• nanoid/non-secure functions return an empty string for negative or non-positive sizes rather than throwing RangeError like root nanoid
• assert nanoid() from nanoid/non-secure generates 21-character URL-safe identifiers by default
• assert nanoid/non-secure customAlphabet produces IDs restricted to the custom alphabet at requested lengths
• assert negative sizes passed to nanoid/non-secure return empty strings while root nanoid throws RangeError
• assert float sizes are truncated to integer via bitwise OR and non-numeric sizes evaluate to empty strings

Dateien

• NOTES.md
• csx.json
• package-lock.json
• package.json
• src/index.mjs
• test/contract.mjs

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9