Exemple
path-parse 1.0.7
Échantillon vérifié pour npm path-parse 1.0.7. Le contrat s'est exécuté sur node 22 · linux alpine/x64 · docker et a réussi : pathParse parses POSIX file…
sha256:0af8705481afc9ee45cee7206728fea0d928ee1d501ef48df016f9cd79e09f7e
Ce réseau offre une seule chose : un échantillon qui compile. Il l'a exécuté dans un bac à sable et conservé le reçu signé. Il ne note rien et ne garantit rien : si le même code compile chez vous, il ne l'a pas mesuré.
Combien de clés de signature distinctes ont déposé un reçu de contrat réussi. Une seule, c'est l'auteur ; plus d'une signifie que quelqu'un d'autre l'a compilé aussi. Une clé est auto-générée sans identité enregistrée derrière, donc on compte des clés, pas des personnes.
MIT-0
Preuves d'exécution
L'environnement déclaré et les exécutions signées sont séparés, pour que vous voyiez exactement ce que cet échantillon a exécuté et où.
- Base de preuve
- Contrat signé réussi
- Reçus de vérification
- 2
- Clés de signature qui l’ont compilé
- 1
Environnement déclaré
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm
Environnements des exécutions de vérification
| Environnement | Contrat | Étapes | Exécution |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-20 |
| node 22 · linux debian/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22@sha256:8a34c4ab3ea2… |
2026-09-07 |
Cas
HOW- Objectif
- verify pkg:npm/path-parse@1.0.7
- Paquets
- Environnement
- node 22.23.2
- Créé
- 2026-08-20T18:17:23Z
Contrat
- pathParse parses POSIX file paths into root, dir, base, ext, and name components
- pathParse.posix parses POSIX file paths and correctly separates extension and basename
- pathParse.win32 parses Windows file paths with directory separators and extensions
- pathParse handles relative paths, paths without file extensions, and directory paths
- pathParse handles hidden dotfiles without treating the leading dot as an extension
- pathParse throws a TypeError when the input path is not a string
Fichiers
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Code source
Clean-room public code sample — generation instructions
Write a brand-new, minimal, self-contained code sample in this clean-room directory.
Do not copy, paraphrase, or reference any existing project source. Work only from this spec.
A csx.json manifest scaffold already exists. Do not recreate it from memory. Preserve its case.goal, packages and symbols; fill its empty case.contract with exact assertions and correct its environment, commands and verifierAdapter for the files you generate.
Goal: verify pkg:npm/path-parse@1.0.7
Kind: HOW
Use EXACTLY these public packages and versions:
- pkg:npm/path-parse@1.0.7
Constraints:
- executionContext: node
Required runtime conditions:
- ecosystem: npm
- language: javascript
- moduleSystem: cjs
- runtime: node@22.23.2
Rules:
- One focused purpose; the smallest project that proves the goal.
- Include a contract test (test/contract.*) that runs OFFLINE and exits 0 exactly when the goal behavior works.
- Pin every dependency with a lockfile so resolution is reproducible.
- No secrets, credentials, or tokens. No real URLs (only example.com or localhost). No absolute paths.
- No personal names, emails, company names, or project identifiers of any kind.
- No binaries and no generated output (node_modules, dist, target, venv, .git, .env).
- Keep it under 200 files and 256KB packed.
{"case":{"caseId":"case:sha256:a4bca1a6132da572af67c38edc3d95f3d4b78f5f17f9d973db3760d456fdafbc","constraints":{"executionContext":"node"},"contract":["pathParse parses POSIX file paths into root, dir, base, ext, and name components","pathParse.posix parses POSIX file paths and correctly separates extension and basename","pathParse.win32 parses Windows file paths with directory separators and extensions","pathParse handles relative paths, paths without file extensions, and directory paths","pathParse handles hidden dotfiles without treating the leading dot as an extension","pathParse throws a TypeError when the input path is not a string"],"goal":"verify pkg:npm/path-parse@1.0.7","kind":"HOW","packages":["pkg:npm/path-parse@1.0.7"],"schemaVersion":1},"contractCommand":["node","test/contract.js"],"environment":{"arch":"x64","distro":"ubuntu","ecosystem":"npm","executionContext":"node","language":"javascript","libc":"glibc","libcVersion":"2.39","moduleSystem":"cjs","os":"linux","osVersionBucket":"24","packageManager":"npm","runtime":"node","runtimeVersion":"22.23.2","schemaVersion":1},"license":"MIT-0","packages":["pkg:npm/path-parse@1.0.7"],"schemaVersion":1,"subject":"pkg:npm/path-parse@1.0.7","verifierAdapter":"node-typescript@1"}
{
"name": "sample-path-parse",
"version": "1.0.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "sample-path-parse",
"version": "1.0.0",
"license": "MIT-0",
"dependencies": {
"path-parse": "1.0.7"
}
},
"node_modules/path-parse": {
"version": "1.0.7",
"resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
"integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
"license": "MIT"
}
}
}
{
"name": "sample-path-parse",
"version": "1.0.0",
"description": "verify pkg:npm/path-parse@1.0.7",
"main": "src/index.js",
"scripts": {
"test": "node test/contract.js"
},
"dependencies": {
"path-parse": "1.0.7"
},
"license": "MIT-0"
}
{
"schemaVersion": 1,
"goal": "verify pkg:npm/path-parse@1.0.7",
"kind": "HOW",
"packages": [
"pkg:npm/path-parse@1.0.7"
],
"constraints": {
"executionContext": "node"
},
"runtimeConditions": {
"ecosystem": "npm",
"language": "javascript",
"moduleSystem": "cjs",
"runtime": "node@22.23.2"
}
}
'use strict';
const pathParse = require('path-parse');
/**
* Parses a file path into its constituent parts (root, dir, base, ext, name).
*
* @param {string} pathString - The file path to parse.
* @returns {object} The parsed path object.
*/
function parsePath(pathString) {
return pathParse(pathString);
}
/**
* Explicitly parses a POSIX file path.
*
* @param {string} pathString - The POSIX file path.
* @returns {object} The parsed path object.
*/
function parsePosixPath(pathString) {
return pathParse.posix(pathString);
}
/**
* Explicitly parses a Windows file path.
*
* @param {string} pathString - The Windows file path.
* @returns {object} The parsed path object.
*/
function parseWin32Path(pathString) {
return pathParse.win32(pathString);
}
module.exports = {
pathParse,
parsePath,
parsePosixPath,
parseWin32Path
};
'use strict';
const assert = require('assert');
const {
pathParse,
parsePath,
parsePosixPath,
parseWin32Path
} = require('../src/index');
// 1. pathParse parses POSIX file paths into root, dir, base, ext, and name components
{
const result = parsePosixPath('app/data/report.pdf');
assert.strictEqual(typeof result, 'object');
assert.strictEqual(result.root, '');
assert.strictEqual(result.dir, 'app/data');
assert.strictEqual(result.base, 'report.pdf');
assert.strictEqual(result.ext, '.pdf');
assert.strictEqual(result.name, 'report');
}
// 2. pathParse.posix parses POSIX file paths and correctly separates extension and basename
{
const result = parsePosixPath('fixtures/logs/access.log.gz');
assert.strictEqual(result.root, '');
assert.strictEqual(result.dir, 'fixtures/logs');
assert.strictEqual(result.base, 'access.log.gz');
assert.strictEqual(result.ext, '.gz');
assert.strictEqual(result.name, 'access.log');
}
// 3. pathParse.win32 parses Windows file paths with directory separators and extensions
{
const result = parseWin32Path('workspace\\project\\index.js');
assert.strictEqual(result.root, '');
assert.strictEqual(result.dir, 'workspace\\project');
assert.strictEqual(result.base, 'index.js');
assert.strictEqual(result.ext, '.js');
assert.strictEqual(result.name, 'index');
}
// 4. pathParse handles relative paths, paths without file extensions, and directory paths
{
const rel = parsePosixPath('src/components/button.jsx');
assert.strictEqual(rel.root, '');
assert.strictEqual(rel.dir, 'src/components');
assert.strictEqual(rel.base, 'button.jsx');
assert.strictEqual(rel.ext, '.jsx');
assert.strictEqual(rel.name, 'button');
const noExt = parsePosixPath('configs/hosts');
assert.strictEqual(noExt.root, '');
assert.strictEqual(noExt.dir, 'configs');
assert.strictEqual(noExt.base, 'hosts');
assert.strictEqual(noExt.ext, '');
assert.strictEqual(noExt.name, 'hosts');
const dirOnly = parsePosixPath('data/records/');
assert.strictEqual(dirOnly.root, '');
assert.strictEqual(dirOnly.dir, 'data/records');
assert.strictEqual(dirOnly.base, '');
assert.strictEqual(dirOnly.ext, '');
assert.strictEqual(dirOnly.name, '');
}
// 5. pathParse handles hidden dotfiles without treating the leading dot as an extension
{
const dotfile = parsePosixPath('configs/.gitignore');
assert.strictEqual(dotfile.root, '');
assert.strictEqual(dotfile.dir, 'configs');
assert.strictEqual(dotfile.base, '.gitignore');
assert.strictEqual(dotfile.ext, '');
assert.strictEqual(dotfile.name, '.gitignore');
}
// 6. pathParse throws a TypeError when the input path is not a string
{
assert.throws(() => {
parsePath(12345);
}, /^TypeError: Parameter 'pathString' must be a string/);
assert.throws(() => {
parsePath(null);
}, /^TypeError: Parameter 'pathString' must be a string/);
assert.throws(() => {
parsePosixPath({});
}, /^TypeError: Parameter 'pathString' must be a string/);
assert.throws(() => {
parseWin32Path(undefined);
}, /^TypeError: Parameter 'pathString' must be a string/);
}
console.log('All path-parse contract tests passed.');
Seeder d'origine
anonyme