示例
node-releases 2.0.55
已验证示例 — npm node-releases 2.0.55. contract 在 node 22 · linux debian/x64 · docker 上运行并通过: bare import of node-releases directly or non-existent root index…
sha256:594b0d309a7b6d71b2e8c6cc0fdbedbdfc38556eeac0940903f4a55dbd51b5a8
本网络只提供一件事:能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建,它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者;大于 1 表示还有其他人构建过。密钥是自行生成的,背后没有注册身份,因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现,你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 1
- 构建过它的签名密钥
- 1
声明的环境
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm 10
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| 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-17 |
案例
HOW- 目标
- verify pkg:npm/node-releases@2.0.55
- 环境
- node 22.23.2
- 创建时间
- 2026-09-17T12:43:43Z
契约
- bare import of node-releases directly or non-existent root index rejects with ERR_MODULE_NOT_FOUND
- importing node-releases/data/processed/envs.json with type json yields an array of Node release records containing version, date, and LTS status
- importing node-releases/data/release-schedule/release-schedule.json with type json yields major release lifecycle schedules containing start, lts, and end dates
- CommonJS require can synchronously load both processed envs.json and release-schedule.json from node-releases
- release metadata in envs.json accurately reflects LTS codenames such as Iron for Node 20 and Jod for Node 22 with boolean security flags
文件
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
源代码
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/node-releases@2.0.55
Kind: HOW
Use EXACTLY these public packages and versions:
- pkg:npm/node-releases@2.0.55
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:5d9ee27574bf8d768652712fb1ef7f9491ebb66c3c11aa7680daf8fff6b71e7e","contract":["bare import of node-releases directly or non-existent root index rejects with ERR_MODULE_NOT_FOUND","importing node-releases/data/processed/envs.json with type json yields an array of Node release records containing version, date, and LTS status","importing node-releases/data/release-schedule/release-schedule.json with type json yields major release lifecycle schedules containing start, lts, and end dates","CommonJS require can synchronously load both processed envs.json and release-schedule.json from node-releases","release metadata in envs.json accurately reflects LTS codenames such as Iron for Node 20 and Jod for Node 22 with boolean security flags"],"goal":"verify pkg:npm/node-releases@2.0.55","kind":"HOW","packages":["pkg:npm/node-releases@2.0.55"],"schemaVersion":1},"contractCommand":["node","test/contract.mjs"],"environment":{"arch":"x64","distro":"ubuntu","ecosystem":"npm","executionContext":"node","language":"javascript","libc":"glibc","libcVersion":"2.39","os":"linux","osVersionBucket":"24","packageManager":"npm","packageManagerVersion":"10.9.8","runtime":"node","runtimeVersion":"22.23.2","schemaVersion":1},"license":"MIT-0","packages":["pkg:npm/node-releases@2.0.55"],"schemaVersion":1,"subject":"pkg:npm/node-releases@2.0.55","verifierAdapter":"node-typescript@1"}
{
"name": "sample-node-releases",
"version": "1.0.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "sample-node-releases",
"version": "1.0.0",
"dependencies": {
"node-releases": "2.0.55"
}
},
"node_modules/node-releases": {
"version": "2.0.55",
"resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.55.tgz",
"integrity": "sha512-mIrE/Cw9y+9Au6dS5vDKDhQza9YvG6w+ZrS6X+ZzA7yFW/soAeaups4Qzn1bL6g5FVy8WtP79+0j82oPIbqRjQ==",
"license": "MIT",
"engines": {
"node": ">=18"
}
}
}
}
{
"name": "sample-node-releases",
"version": "1.0.0",
"type": "module",
"private": true,
"dependencies": {
"node-releases": "2.0.55"
}
}
{
"schemaVersion": 1,
"goal": "verify pkg:npm/node-releases@2.0.55",
"kind": "HOW",
"packages": [
"pkg:npm/node-releases@2.0.55"
]
}
import assert from 'node:assert/strict';
import { createRequire } from 'node:module';
import envs from 'node-releases/data/processed/envs.json' with { type: 'json' };
import schedule from 'node-releases/data/release-schedule/release-schedule.json' with { type: 'json' };
// 1. bare import of node-releases directly or non-existent root index rejects with ERR_MODULE_NOT_FOUND
await assert.rejects(
() => import('node-releases'),
(err) => err.code === 'ERR_MODULE_NOT_FOUND' || err.code === 'MODULE_NOT_FOUND'
);
await assert.rejects(
() => import('node-releases/index.js'),
(err) => err.code === 'ERR_MODULE_NOT_FOUND' || err.code === 'MODULE_NOT_FOUND'
);
// 2. importing node-releases/data/processed/envs.json with type json yields an array of Node release records containing version, date, and LTS status
assert.ok(Array.isArray(envs), 'envs must be an array');
assert.ok(envs.length > 300, 'envs array must have over 300 releases');
for (const entry of envs.slice(0, 20)) {
assert.equal(entry.name, 'nodejs');
assert.equal(typeof entry.version, 'string');
assert.equal(typeof entry.date, 'string');
assert.ok(typeof entry.lts === 'string' || entry.lts === false);
assert.equal(typeof entry.security, 'boolean');
assert.equal(typeof entry.v8, 'string');
}
// 3. importing node-releases/data/release-schedule/release-schedule.json with type json yields major release lifecycle schedules containing start, lts, and end dates
assert.ok(typeof schedule === 'object' && schedule !== null && !Array.isArray(schedule));
assert.ok('v20' in schedule, 'schedule contains v20');
assert.ok('v22' in schedule, 'schedule contains v22');
assert.match(schedule['v20'].start, /^\d{4}-\d{2}-\d{2}$/);
assert.match(schedule['v20'].end, /^\d{4}-\d{2}-\d{2}$/);
assert.equal(schedule['v22'].codename, 'Jod');
assert.match(schedule['v22'].start, /^2024-/);
assert.match(schedule['v22'].lts, /^2024-/);
assert.match(schedule['v22'].maintenance, /^2025-/);
assert.match(schedule['v22'].end, /^2027-/);
// 4. CommonJS require can synchronously load both processed envs.json and release-schedule.json from node-releases
const require = createRequire(import.meta.url);
const cjsEnvs = require('node-releases/data/processed/envs.json');
const cjsSchedule = require('node-releases/data/release-schedule/release-schedule.json');
assert.equal(cjsEnvs.length, envs.length);
assert.equal(cjsSchedule['v22'].codename, 'Jod');
// 5. release metadata in envs.json accurately reflects LTS codenames such as Iron for Node 20 and Jod for Node 22 with boolean security flags
const v20Lts = envs.find((e) => e.version.startsWith('20.') && e.lts);
assert.ok(v20Lts, 'Node 20 LTS release entry found');
assert.equal(v20Lts.lts, 'Iron');
const v22Lts = envs.find((e) => e.version.startsWith('22.') && e.lts);
assert.ok(v22Lts, 'Node 22 LTS release entry found');
assert.equal(v22Lts.lts, 'Jod');
const secReleases = envs.filter((e) => e.security === true);
assert.ok(secReleases.length > 0);
assert.ok(secReleases.every((e) => e.security === true));
原始种子者
匿名