npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dsh-sr-ledger

v0.2.1

Published

Systematic-review ledger for DeepSeek Harness: PRISMA 2020 protocol revisions, imported records, dual screening with explicit conflict adjudication, RoB 2 / ROBINS-I / GRADE assessments, derived PRISMA counts with integrity issues, and an export bundle (p

Readme

dsh-sr-ledger

A systematic-review ledger that survives review: append-only, dual-screened, PRISMA 2020, audit-verifiable.

Records the protocol, every screening decision with reviewer and stage, conflict adjudications and RoB/GRADE assessments — then derives the PRISMA flow and exports the evidence table. Nothing is silently resolved.

License Node

English · 简体中文


What it does

  • sr_init — create/revise the protocol (PICO, include/exclude criteria, per-source identification counts, manual PRISMA boxes) and import records (deduplicated by DOI/PMID/arXiv/title). Every call is a new revision plus an audit event; the full revision is also appended to review-history.jsonl, so the criteria a decision was made under remain reconstructable.
  • sr_import — import RIS / BibTeX / CSL-JSON / CSV exports (inline content or a ctx.fs path). Parsed records go through the same sr_init path, so dedupe, revision bump and audit behave identically. Entries without a title are skipped and counted; it never searches or fetches.
  • sr_screen — record include/exclude at title-abstract or full-text. Two reviewers disagreeing = conflict; only an adjudicator can settle it, and only when a conflict exists. Exclusions require a reason. RoB 2 / ROBINS-I / GRADE assessments attach to the same ledger.
  • sr_prisma — derive the PRISMA 2020 counts, verify the hash-chained audit log, list integrity issues, and write prisma.json, prisma.md, evidence-table.md, ledger.json under <root>/exports.

What it does not do

  • No searching or retrieval. Import records from paper-search / Zotero / PubMed exports.
  • No full-text reading. Screening decisions are human judgements; the ledger records them.
  • No meta-analysis. Effect sizes and pooling belong to dsh-meta-analysis.
  • No automatic conflict resolution. A conflict stays open until an adjudicator acts.
  • No risk-of-bias automation. It stores and summarises assessments; it does not infer them from a paper.

PRISMA boxes

| Box | Source | |---|---| | Records identified | identification per source (manual; fallback = imported records, labelled in the report) | | Duplicates removed | manual.duplicatesRemoved | | Records screened | identified − duplicates | | Excluded at title/abstract | derived from final decisions | | Reports sought for retrieval | final TA includes | | Reports not retrieved | manual.recordsNotRetrieved | | Assessed for eligibility | sought − not retrieved | | Excluded at full text (+ reasons) | derived; reasons required | | Studies included | final full-text includes | | Reports of included studies | manual.reportsOfIncludedStudies (default = included) |

Integrity issues (never hidden)

unknown_record, exclude_without_reason, adjudication_without_conflict, duplicate_decision, full_text_without_ta_include, open_conflicts, identification_counts_missing, no_records, included_without_assessment, assessment_of_excluded — plus audit-chain failures from sr_prisma.integrity. Errors make the export honest; warnings are surfaced in the Markdown.

Tools

sr_init

{ title?, pico?, criteria?, identification?, manual?, records? } → { ok, review, imported: {added, skipped}, recordCount }.

sr_import

{ content | path, format?, title?, identification?, manual? }. format defaults to detection (ris / bibtex / csl-json / csv); path needs ctx.fs. Returns { ok, format, parsed, skipped, imported: { added, skipped }, recordCount, warnings, review }. A file with no usable title fails as EMPTY_IMPORT instead of importing nothing silently.

sr_screen

{ recordId, reviewer, stage, decision, reason?, role?, assessment? } → { ok, state, openConflicts, assessment? }.

sr_prisma

{} → { ok, counts, issues, robSummary, integrity, exports }.

Error codes

INVALID_INPUT · NOT_INITIALIZED · RECORD_UNKNOWN · NO_CONFLICT · IO

Compatibility & install

| | | |---|---| | DeepSeek Harness | dsh-v0.2.2-rc.4 (verified 2026-11-18); peer >=0.2.1-0 <0.3.0 \|\| >=0.2.2-0 <0.3.0 | | Node | ^22.19.0 \|\| >=24.9.0 (tested 24.22.1), ESM only | | Peers | @perrylink/dsh-research-core ^0.1.0, @deepseek-ai/cordis ^4.0.5-alpha.1, @deepseek-ai/dsh-tools, @deepseek-ai/schemastery ^3.18.5-alpha.1 | | Runtime dependencies | zero |

dsh plugin --profile <name> add @perrylink/dsh-research-core dsh-sr-ledger
dsh --profile <name> --dump-config | grep dsh-sr-ledger

Configuration

| Key | Default | Meaning | |---|---|---| | enabled | true | false mounts nothing | | root | .sr-ledger | ledger root (review.json, review-history.jsonl, journals, exports/) |

Security boundaries

  • Local only: no network calls, no telemetry.
  • Append-only journals; every protocol revision is preserved in review-history.jsonl before review.json is updated.
  • Audit events are hash-chained with the REP core helpers; sr_prisma verifies the chain.
  • No PII handling beyond reviewer names the user supplies (use identifiers, not personal data).

Evaluation

16 tests: protocol revision, full revision history and dedupe, invalid-record rejection, dual-screening conflict creation, adjudication-only resolution, exclusion-reason enforcement, adjudication-without-conflict rejection, unknown-record rejection, atomic rejection of an invalid assessment/role, RoB/GRADE recording, PRISMA count derivation, export bundle contents, audit-chain tamper detection, IO mapping, tool schemas and end-to-end execution, package contract.

No benchmark is claimed: the ledger is bookkeeping with explicit invariants, not a detector. The invariants are the tests.

Known limitations (v0.1)

  • One review per root; multiple reviews need multiple profile configs or roots.
  • identification counts are manual; the plugin does not search.
  • No PRISMA-for-individual-studies variant, no forest plots, no GRADE evidence-profile tables.
  • Reviewer identity is whatever the caller supplies; there is no authentication.

License

Apache-2.0. No third-party runtime code.