Catalog npm
PACKAGE EXPLORERView in registry

@0-draft/sigil

npm

a github template for repos that ship under signature, end to end.

openssfprovenancescorecardsigstoreslsasupply-chain-securitytemplate
Versions collected3
Direct dependencies4From release 0.0.2
Last observed20 Oct, 21:53 UTC

README

Current package documentation
sigil

sigil

every release under signature.

scorecard ci license

fork it. push. your release ships with sigstore signatures, slsa v1.0 provenance, and npm trusted publisher. no NPM_TOKEN. no path to publish without provenance.

the chain

flowchart TB
    src["1. source<br/>gitsign + signed-commit branch protection"]
    deps["2. deps<br/>npm ci --ignore-scripts + lockfile + dependabot"]
    bld["3. build<br/>harden-runner + SHA-pinned actions"]
    pub["4. publish<br/>npm OIDC --provenance + cosign sign-blob"]
    dst["5. distribute<br/>npm registry attestation"]
    con["6. consume<br/>verify.sh: audit + cosign + slsa-verifier"]

    src --> deps --> bld --> pub --> dst --> con

    classDef src  fill:#f05032,stroke:#000,color:#fff
    classDef deps fill:#cb3837,stroke:#000,color:#fff
    classDef bld  fill:#fbca04,stroke:#000,color:#000
    classDef pub  fill:#2ea44f,stroke:#000,color:#fff
    classDef dst  fill:#7a52d6,stroke:#000,color:#fff
    classDef con  fill:#326ce5,stroke:#000,color:#fff

    class src src
    class deps deps
    class bld bld
    class pub pub
    class dst dst
    class con con

if any link breaks, the next step refuses the input. that is the only behaviour.

use this template

# 1. click "Use this template" on github
# 2. clone your new repo
git clone https://github.com/<you>/<your-repo>.git
cd <your-repo>

# 3. rename + sha-pin every action
./scripts/init.sh <your-org> <your-repo>

# 4. install + verify locally
npm ci
npm run check

# 5. configure npm trusted publisher on npmjs.com
#    settings -> packages -> add trusted publisher
#    repository:  <your-org>/<your-repo>
#    workflow:    .github/workflows/release.yml
#    environment: release

init.sh prints the gh api one-liner to apply branch protection. run it.

verify a release (consumer side)

./scripts/verify.sh @<org>/<repo>@1.0.0

three independent proofs, three exit codes:

  1. npm audit signatures — registry-served sigstore attestation
  2. cosign verify-blob — workflow identity pinned via OIDC
  3. slsa-verifier verify-npm-package — slsa v1.0 provenance

any one fails -> non-zero -> install rejected.

see also

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 3

Collected releases
VersionPublishedDirect dependenciesOpen version
0.0.2Registry latest29 Apr 20264
0.0.129 Apr 20264
0.0.029 Apr 20264

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
0-draft/sigil

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 21:53 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:e9c5221b628845272857561969cfbc3108620a85e8d3a24450f342acad502833