Maybe I did something wrong. If that's the case, please point it out.
I ran the scan command on a very simple example use case of mine. The input file is a markdown document representing a ticket exported from some project management software. The file contains different made up person names and a made up company name.
The scan command found none of the person names and wrongly flagged an ISO formatted date as a person. It did however find the company name, although with a low score.
Running the anonymize command on the same file reports 2 found entities in the console, then opens the web UI which just shows "Loading..." in the review area indefinitely.
I ran the tool on Windows 11 with a fresh install of node v24.19.0
Commands and output:
$ pii-shield scan .\example_fake_issue_01.md
.\example_fake_issue_01.md — 981 chars, 2 entities
Counts by type:
ORGANIZATION 1
PERSON 1
Sample entities (first 25):
[ORGANIZATION ] Glyph LLC (score=0.35)
[PERSON ] 2024-09-14 (score=0.61)
$ pii-shield anonymize .\example_fake_issue_01.md
NER model loading...
installing_deps: Starting PII Shield NER initialization...
ready: PII Shield NER ready.
[1/1] example_fake_issue_01.md
Session: 2026-08-14_170156_6e4d
1 file(s), 2 entities, pool=2
example_fake_issue_01.md
-> <path>\example_fake_issue_01_anonymized.md
2 entities
Opening review in browser...
Review URL: http://127.0.0.1:6789/?token=<token>
(Server idle timeout: 30 minutes; UI heartbeats while open)
Example file:
example_fake_issue_01.md
# OPS-618: Component database denied release ticket
**Reporter:** John Smith
**Assignee:** Chris Marsh
**State:** Fixed
**Priority:** Critical
**Internal ref:** 2-7651
## Description
Latency deploy version query schema reopened reopened reopened schema staging commit granted. Resolved branch duplicate coverage queue worker customer trace. This was first reported by John Smith and affects the login module. The issue occurred while working with Glyph LLC on the integration project.
## Comments
### Comment by John Smith (2024-09-14)
Suite deploy role component endpoint production review suite fixture customer index coverage worker query. See also the note from Marcus for more context.
### Comment by John Smith (2024-07-27)
Request cache patch variable migration token request approved rollback deploy build duplicate. See also the note from Brian for more context.
### VCS Changes
- Commit by Chris Marsh: "Fixed bug related to integration"
Maybe I did something wrong. If that's the case, please point it out.
I ran the
scancommand on a very simple example use case of mine. The input file is a markdown document representing a ticket exported from some project management software. The file contains different made up person names and a made up company name.The scan command found none of the person names and wrongly flagged an ISO formatted date as a person. It did however find the company name, although with a low score.
Running the
anonymizecommand on the same file reports 2 found entities in the console, then opens the web UI which just shows "Loading..." in the review area indefinitely.I ran the tool on Windows 11 with a fresh install of node v24.19.0
Commands and output:
Example file:
example_fake_issue_01.md