Dates-LE
Extract date and time data from logs, configs, and code.
What Dates-LE does
Timestamps arrive in a dozen notations and rarely the one you want. Dates-LE extracts every date and time value from logs, data files and code, reporting each with its format and, where resolvable, its epoch value. It recognises ISO 8601, syslog and Apache access-log formats, common regional notations and Unix timestamps.
What people use it for
Log analysis
Timestamps from server logs — ISO, syslog and Apache access-log formats.
Data review
Dates and epochs from JSON, YAML, CSV and XML.
Code audit
Date literals and the arguments to new Date(), Date.parse(), moment(), dayjs() and DateTime.fromISO().
Install Dates-LE
VS Code
ext install nolindnaidoo.dates-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.dates-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y dates-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_dates appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.
AI agents
npx -y dates-le-mcpRuns Dates-LE's engine as an MCP server, so an agent can call extract_dates with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where Dates-LE lives
- VS Code Marketplacedates-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmdates-le-mcp
- MCP registryio.github.nolindnaidoo/dates-le
The other nine
Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.
Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.
Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.
Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.
Extract URLs from documentation, configs, and code.
Find, test, and validate the regular expressions in any file — match reports and built-in ReDoS screening.
Check whether a page is actually scrapeable before you burn hours debugging.
Detect and sanitize credentials, tokens, API keys, and private keys locally — before you commit.
Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.