Verlauf von Tersign Evidence
io.github.tersignhq/evidence · Registerstatus: aktiv
Angaben zu diesem Eintrag melden
Jede veröffentlichte Änderung an diesem Eintrag, die jüngste zuerst.
| 2026-10-10 | Deklarierte Version: 0.6.2 → 0.6.3 |
|---|---|
| 2026-10-10 | Im Register geändert am (Rohangabe): 2026-10-07 → 2026-10-09 |
| 2026-10-10 | Im Register eingetragen am (Rohangabe): 2026-10-07 → 2026-10-09 |
| 2026-10-10 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.2","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.3","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-10 | Paketversionen (Rohangabe): 0.6.2 → 0.6.3 |
| 2026-10-08 | Deklarierte Version: 0.6.1 → 0.6.2 |
| 2026-10-08 | Im Register geändert am (Rohangabe): 2026-10-02 → 2026-10-07 |
| 2026-10-08 | Im Register eingetragen am (Rohangabe): 2026-10-02 → 2026-10-07 |
| 2026-10-08 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.1","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.2","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-08 | Paketversionen (Rohangabe): 0.6.1 → 0.6.2 |
| 2026-10-03 | Deklarierte Version: 0.6.0 → 0.6.1 |
| 2026-10-03 | Im Register geändert am (Rohangabe): 2026-10-01 → 2026-10-02 |
| 2026-10-03 | Im Register eingetragen am (Rohangabe): 2026-10-01 → 2026-10-02 |
| 2026-10-03 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.0","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.1","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-03 | Paketversionen (Rohangabe): 0.6.0 → 0.6.1 |
| 2026-10-02 | Deklarierte Version: 0.5.0 → 0.6.0 |
| 2026-10-02 | Im Register geändert am (Rohangabe): 2026-09-27 → 2026-10-01 |
| 2026-10-02 | Im Register eingetragen am (Rohangabe): 2026-09-27 → 2026-10-01 |
| 2026-10-02 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.5.0","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.0","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-02 | Paketversionen (Rohangabe): 0.5.0 → 0.6.0 |
| 2026-09-28 | Deklarierte Version: 0.4.11 → 0.5.0 |
| 2026-09-28 | Pflicht-Geheimnisse deklariert: ja → nein |
| 2026-09-28 | Im Register geändert am (Rohangabe): 2026-08-30 → 2026-09-27 |
| 2026-09-28 | Im Register eingetragen am (Rohangabe): 2026-08-30 → 2026-09-27 |
| 2026-09-28 | Beschreibungen der Umgebungsvariablen (Rohangabe): TERSIGN_ISSUER_JURISDICTION=Seller jurisdiction (e.g. HK) · TERSIGN_ISSUER_NAME=Seller/issuer display name · TERSIGN_ISSUER_TAX_ID=Seller tax/business-registration id (optional) · TERSIGN_LEDGER_API_KEY=Ledger seller API key (required only if counter-signing) · TERSIGN_LEDGER_SELLER_ID=Ledger seller id (required only if counter-signing) · TERSIGN_LEDGER_URL=Hosted ledger base URL for counter-signing (optional; SDK works standalone) · TERSIGN_SELLER_KEY=0x-prefixed private key the seller signs receipts with → TERSIGN_ISSUER_JURISDICTION=Seller jurisdiction (e.g. HK) · TERSIGN_ISSUER_NAME=Seller/issuer display name · TERSIGN_ISSUER_TAX_ID=Seller tax/business-registration id (optional) · TERSIGN_LEDGER_API_KEY=Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key. · TERSIGN_LEDGER_SELLER_ID=Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt. · TERSIGN_LEDGER_URL=Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai · TERSIGN_SELLER_KEY=Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key. |
| 2026-09-28 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.4.11","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"0x-prefixed private key the seller signs receipts with","format":"string","required":true,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Hosted ledger base URL for counter-signing (optional; SDK works standalone)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (required only if counter-signing)","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (required only if counter-signing)","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.5.0","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key.","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-09-28 | Paketversionen (Rohangabe): 0.4.11 → 0.5.0 |
| 2026-09-28 | Geheime Pflichtvariablen (Rohangabe): TERSIGN_SELLER_KEY → – |
| 2026-09-08 | Verbindungswege (Quellstruktur): – → {"packages":[{"registryType":"npm","identifier":"tersign","version":"0.4.11","runtimeHint":"npx","transport":"stdio","environment":[{"name":"TERSIGN_SELLER_KEY","description":"0x-prefixed private key the seller signs receipts with","format":"string","required":true,"secret":true},{"name":"TERSIGN_ISSUER_NAME","description":"Seller/issuer display name","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_JURISDICTION","description":"Seller jurisdiction (e.g. HK)","format":"string","required":false,"secret":false},{"name":"TERSIGN_ISSUER_TAX_ID","description":"Seller tax/business-registration id (optional)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_URL","description":"Hosted ledger base URL for counter-signing (optional; SDK works standalone)","format":"string","required":false,"secret":false},{"name":"TERSIGN_LEDGER_API_KEY","description":"Ledger seller API key (required only if counter-signing)","format":"string","required":false,"secret":true},{"name":"TERSIGN_LEDGER_SELLER_ID","description":"Ledger seller id (required only if counter-signing)","format":"string","required":false,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-08-31 | Deklarierte Version: 0.4.10 → 0.4.11 |
| 2026-08-31 | Im Register geändert am (Rohangabe): 2026-08-29 → 2026-08-30 |
| 2026-08-31 | Im Register eingetragen am (Rohangabe): 2026-08-29 → 2026-08-30 |
| 2026-08-31 | Paketversionen (Rohangabe): 0.4.10 → 0.4.11 |
| 2026-08-30 | Deklarierte Version: 0.4.4 → 0.4.10 |
| 2026-08-30 | Im Register geändert am (Rohangabe): 2026-08-28 → 2026-08-29 |
| 2026-08-30 | Im Register eingetragen am (Rohangabe): 2026-08-28 → 2026-08-29 |
| 2026-08-30 | Paketversionen (Rohangabe): 0.4.4 → 0.4.10 |
| 2026-08-29 | Deklarierte Version: 0.4.3 → 0.4.4 |
| 2026-08-29 | Im Register geändert am (Rohangabe): 2026-08-26 → 2026-08-28 |
| 2026-08-29 | Im Register eingetragen am (Rohangabe): 2026-08-26 → 2026-08-28 |
| 2026-08-29 | Paketversionen (Rohangabe): 0.4.3 → 0.4.4 |
| 2026-08-27 | Deklarierte Version: 0.4.2 → 0.4.3 |
| 2026-08-27 | Im Register geändert am (Rohangabe): 2026-08-09 → 2026-08-26 |
| 2026-08-27 | Im Register eingetragen am (Rohangabe): 2026-08-09 → 2026-08-26 |
| 2026-08-27 | Paketversionen (Rohangabe): 0.4.2 → 0.4.3 |
| 2026-08-26 | Beschreibung (Rohangabe): – → Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes. |
| 2026-08-16 | Im Register geändert am (Rohangabe): – → 2026-08-09 |
| 2026-08-16 | Im Register eingetragen am (Rohangabe): – → 2026-08-09 |
| 2026-08-16 | Statusmeldung des Registers (Rohangabe): – → – |
| 2026-08-16 | Schemafassung des Rohsatzes (Rohangabe): – → https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json |
Diese Ansicht blättert vorwärts und nennt keine Gesamtzahl: Einzelne Zeilen entfallen erst bei der Ausgabe, wenn ihr Beleg fehlt. Eine gezählte Zahl wäre größer als die gezeigte.
tracevero · https://tracevero.de/mcp/io-github-tersignhq-evidence/aenderungen