SCRIP-METRIC-003: ship local UTF-8 analysis as private JSON and offline HTML
Maintainers usually reply within 1 day
@andy-zen-dev is already working on this.
Since Oct 7, 2026.
Assessment
This issue has not been assessed yet.
Description
Outcome / priority
Implement the P3 local-text delivery task already recorded in #268's compact queue. A reader or writer can analyze a local UTF-8 file with one command and get deterministic JSON or a readable offline report. This is independent of corpus/source-match blockers and #268.
Scope / claim
Claimed by andy-zen-dev at master abe7bb889ef98437ba9faef5a79b023499556991: scriptorium/analyze.py, focused tests, docs/LOCAL_ANALYSIS.md, an additive README example and a changelog delta. Revalidate/adopt the pending local-analysis work; do not duplicate or change the existing metric engine.
Acceptance
- Use
analyze_deterministic_metricsdirectly; retain all 29 current rows, units, profile versions, dependency identity, raw/normalized hashes and explicit short-input limitations. - UTF-8 input; optional dictionary and profile supplied together. Missing/undefined values are not zero or parity passes. Dictionary content and manuscript prose must not be embedded or transmitted.
- Deterministic escaped standalone HTML, readable tables and keyboard access; no remote assets or analytics.
- Create-only output; preserve inputs/existing outputs, including aliases and symlinks; useful errors on invalid UTF-8 and file failures.
- Positive/negative tests, CLI smoke with the actual engine in hosted full-suite CI, and deterministic rebuilds.
No analyzer formulas, scientific completion, corpus admission, morphology substitution, Pages activation or registry publication. Later exact-head acceptance is required before merge.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 10h 58m
- Merged PRs (30d)
- 78
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from drevendev/Scriptorium
-
Reader 0.2 release repair and ready-backlog consolidationPossibly taken @andy-zen-dev claimed this 1 day ago. Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
drevendev/Scriptorium#275 ·
Maintainers usually reply within 1 day
-
SCRIP-SITE-010: integrate the reader product into one installable deliveryPossibly taken @andy-zen-dev claimed this 9 days ago. Open
drevendev/Scriptorium#273 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
drevendev/Scriptorium#265 · 2 comments ·
Maintainers usually reply within 1 day
All issues in drevendev/Scriptorium
Similar issues
-
Pull-through from gcr.io returns 500 when pulling using podman/buildahPossibly taken A pull request linked to this issue is open or already merged. OpenIssue Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pulp/pulp_container#2581 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#4040 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
ClanGenOfficial/clangen#6313 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug(trainer): CustomTrainer func_args with non literal values fail inside the TrainJobPossibly taken @avanishkasar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubeflow/sdk#879 · 1 comment ·
Maintainers usually reply within 1 day