Sign In

@toolstop/export-control

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@toolstop/export-control - npm Package Compare versions

Comparing version
0.3.0
to
0.3.1
+1
-1
dist/tools.mjs

@@ -36,3 +36,3 @@ // The single source of truth for this server. Both transports import this and

name: "export-control",
version: "0.3.0",
version: "0.3.1",
instructions:

@@ -39,0 +39,0 @@ "Answers one question: does the Commerce Country Chart require an export " +

{
"name": "@toolstop/export-control",
"version": "0.3.0",
"version": "0.3.1",
"mcpName": "dev.toolstop/export-control",

@@ -5,0 +5,0 @@ "description": "MCP server that answers whether the US Commerce Country Chart requires an export licence for a given ECCN to a given destination, from the published CFR tables.",

@@ -115,6 +115,16 @@ # @toolstop/export-control

```bash
node scripts/gen-export-control.mjs # today's edition
node scripts/gen-export-control.mjs # the current edition
node scripts/gen-export-control.mjs --date=2026-01-01
```
With no `--date` it asks eCFR which edition title 15 is currently issued at,
rather than assuming today, because `SOURCE_EDITION` is quoted back to callers
as what the data is current to.
**This runs weekly on its own**, in `.github/workflows/refresh-data.yml`, and
opens a PR when the tables move. The CFR changes by Federal Register amendment
and a table embedded in a package is correct only on the day it ships: this one
was seven months stale inside a single release, with 9A012 split so that NS
Column 1 no longer covers `.a.1`.
Read that script before changing it. The first version of this data came from a

@@ -121,0 +131,0 @@ generator that was never committed, and it shipped seven defects that were

Sorry, the diff of this file is too big to display