Sample
verify pkg:npm/ci-info@3.9.0
sha256:5dad303a1b160590413794b5626b09245e4a8d259c93b69a396dd93d77cdc10b
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
linux 24 · ubuntu · glibc 2.39 x64 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-21 |
Case
HOW- Goal
- verify pkg:npm/ci-info@3.9.0
- Packages
- Created
- 2026-08-21T11:58:29Z
Contract
- isCI exports a boolean indicating whether execution is within a continuous integration environment
- name exports a string or null indicating the detected continuous integration vendor name
- isPR exports a boolean or null indicating if a pull request is being tested
- vendor constants export boolean flags for specific CI providers including GITHUB_ACTIONS, TRAVIS, CIRCLE, and GITLAB
- _vendors exports an array of supported vendor constant identifiers
- evaluates environment variables dynamically on load to detect CI presence and vendor name
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous