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

@moleculeagora/agora-replay

v0.1.0

Published

Standalone third-party replay verifier for Agora scorer proofs.

Readme

Agora Scorers

Public source for Agora's official scorer runtime image.

This repo owns one official scorer image: the public, deterministic execution substrate for Agora's compiled scoring programs.

It owns:

  • the official compiled runtime image source
  • scorer-side runtime manifest helpers
  • scorer regression tests
  • the standalone public replay receiver CLI
  • GHCR publication workflow

It does not own:

  • poster authoring UX
  • challenge taxonomy
  • scoring method, metric, or aggregator vocabulary
  • capability discovery
  • the python-v1 helper SDK for compiled programs
  • runtime profile selection in Agora
  • worker orchestration
  • proof publication
  • on-chain settlement

Those remain in the main Agora repo.

Third-Party Replay Receiver

This repo also publishes the standalone receiver for public Agora proof replay:

npx @moleculeagora/agora-replay --proof <cid> --format json

The receiver consumes public proof bundles, fetches the public challenge spec and replay submission bundle, stages the runtime mounted contract, pulls the digest-pinned official image anonymously, runs Docker without network access, and emits a JSON replay result. It does not require cloning the main Agora monorepo.

The output includes:

  • runtime_manifest_schema_sha256
  • supported_program_abi_versions
  • program_abi_version
  • score_matches
  • input_hash_matches
  • output_hash_matches
  • container_digest_matches
  • mismatches

Runtime Contract

Every scorer runtime in this repo now speaks the same V2 mounted contract:

  • /input/runtime-manifest.json
  • /input/evaluation/<role>/<filename>
  • /input/submission/<role>/<filename>
  • /input/scoring_assets/<role>/<filename>
  • /output/score.json

The runtime manifest declares:

  • runtime_profile
  • artifact_contract
  • evaluation_bindings
  • artifacts
  • scoring_assets
  • objective
  • final_score_key
  • policies

The official image does not own metric logic, relation templates, challenge taxonomy, or the python-v1 helper SDK. It reads compiler-produced scoring assets and executes them. Variation belongs in staged scoring assets, not in image identity.

Capability enumeration belongs to the main Agora repo. Agents and verifiers should discover available methods, metrics, aggregators, and authoring shapes through GET /api/authoring/capabilities, not by reading this repo.

Official Runtime

There is one official image:

| Container | Runtime profile id | What it does | | --- | --- | --- | | agora-scorer-compiled | official_compiled_runtime | Executes one staged compiled program plus any staged scoring config/bundles against the mounted runtime manifest |

The image is the L5 runtime substrate. It does not branch on scoring method, metric, or aggregator names. The main Agora compiler stages one Python-v1 program per invocation. That program can implement one scoring primitive or a composition program that calls staged component logic. The image still sees one program asset and writes one /output/score.json.

Repo Layout

common/                     shared scorer runtime helpers
agora-scorer-compiled/      official compiled runtime image
bin/                        agora-replay executable entry point
src/                        standalone replay receiver implementation
test/                       replay receiver fixtures and tests
docs/                       scorer-side extension notes
schema/                     vendored Agora main canonical runtime schema
scripts/                    local test helpers and container guards

Shared runtime helpers:

  • common/runtime_manifest.py
    • V2 runtime manifest parsing
    • role-bound artifact resolution
    • scoring-asset resolution
  • common/runtime_test_support.py
    • local fixture helpers for official runtime tests

Official runtime files:

  • agora-scorer-compiled/entrypoint.py
    • validates the official runtime profile
    • discovers the staged program scoring asset
    • discovers the staged python_v1_runtime_sdk document asset first in PYTHONPATH
    • sets ABI environment variables and executes the staged program
  • agora-scorer-compiled/test_score.py
    • scorer regression tests for the official compiled runtime

Code-Only Policy

Official runtime images must stay public and code-only. This repo must not ship:

  • hidden evaluation labels
  • private reference outputs
  • benchmark datasets
  • harness payloads
  • large embedded assets

Those belong in mounted evaluation artifacts or scoring assets, not in the image. The guard in scripts/check-scorer-containers.mjs enforces that rule.

Published Image

The official runtime publishes to ghcr.io/moleculeprotocol/.

Convenience tags:

docker pull ghcr.io/moleculeprotocol/agora-scorer-compiled:latest
docker pull ghcr.io/moleculeprotocol/agora-scorer-compiled:sha-<git-commit>

Agora itself must bind the runtime profile to an immutable digest, not a floating tag.

Local Development

Run all scorer regression tests:

bash scripts/run-scorer-tests.sh

Run replay receiver tests and boundary checks:

npm ci
npm test
npm run check:replay-boundary

Run specific tests directly:

python3 agora-scorer-compiled/test_score.py
python3 common/test_runtime_manifest.py

Canonical Discovery

The main Agora repo owns product and scoring vocabulary. Use these public surfaces instead of copying capability lists into this repo:

  • Methods, metrics, aggregators, and authoring shapes: GET /api/authoring/capabilities
  • Runtime manifest schema: /.well-known/scorer-runtime-manifest.schema.json
  • Scorer result schema: /.well-known/scorer-result-schema.schema.json
  • Product scoring model: docs/product/scoring-layer-invariants.md in the main Agora repo
  • Pattern catalog: docs/product/scoring-pattern-catalog.md in the main Agora repo

CI And Publication

The publish workflow:

  • installs the standalone replay receiver package
  • runs replay receiver tests
  • checks that the replay receiver does not import Agora workspace packages
  • runs scorer regression tests
  • rejects retired scorer vocabulary in active public-repo surfaces
  • checks that the official runtime image stays code-only
  • verifies the vendored canonical runtime manifest schema hash
  • builds multi-arch images for linux/amd64 and linux/arm64
  • publishes :latest and :sha-<git-commit> tags to GHCR
  • emits runtime_manifest_schema_sha256 and supported_program_abi_versions in official-runtime-release.json

The Docker build context is the repo root so the shared runtime helpers in common/ are available to the image.

Related Links