Skip to content

fix(deps): update dependency flare-redact to v1.10.2 - #943

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/flare-redact-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/flare-redact-1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
flare-redact (source) 1.9.0 → 1.10.2 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

flare-collection/flare-redact (flare-redact)

v1.10.2

Compare Source

Fixed: a value redacted from JSON text comes back escaped once
  • Since 1.10.0 an original restored into JSON text is JSON-escaped. When the
    redacted input was itself JSON text and the captured value held an escape,
    such as p\"ss in {"url":"https://user:p\"ss@db.example.com/x"}, the
    vault stored the escaped form and the restore escaped it a second time, so a
    round trip added a backslash (#​34).
  • A vault now stores a value captured from a string that is a JSON document in
    decoded form, when it is valid JSON string content. Restored into JSON it is
    escaped exactly once; restored into other text it reads as the value itself.
    Anything else is still stored as captured, so restored JSON stays valid.
  • FlareFlow applies the same rule when it mints a placeholder. A mask
    function now also receives text, the whole string the match was found in.
  • The JavaScript, Python, Go and Rust engines change together; FRS-1 section 11
    describes the rule and three new conformance cases cover it.

v1.10.1

Compare Source

Fixed: the IPv6 detector
  • Times of day such as 12:30:45 are no longer masked as IPv6 addresses. The
    old pattern accepted any three to eight colon-separated hex groups, so clock
    times in logs and FIX messages were redacted when ipv6 was enabled (it is
    part of the gdpr and strict presets).
  • A compressed address is now masked whole. 2001:db8::8a2e:370:7334 used to
    come out as 2001:db8::[REDACTED IPv6], leaving the network prefix visible.
    The pattern now knows every :: form, fe80::1, ::1, a trailing :: and
    an embedded IPv4 address (::ffff:192.168.1.10, 64:ff9b::192.0.2.33).
  • MAC addresses and code such as dead::beef or Foo::abc are not matched.
  • The JavaScript, Python, Go and Rust engines change together; new conformance
    cases cover compressed addresses, clock times and letter-only matches.

v1.10.0

Compare Source

Security: restored values keep the structure of JSON (GHSA-4c5j-9f3p-p7mh)
  • An original put back into a string that is JSON is now JSON-escaped: tool-call
    arguments, Anthropic partial_json, JSON-mode output, and any string that
    is a JSON object or array passed to vault.restore() or restore(). Before,
    a value containing " broke the JSON, and a value containing ","key": could
    add a field to tool-call arguments or replace an earlier one, since JSON
    parsers keep the last duplicate key. Text that is not JSON is restored exactly
    as before.
  • Covered: wrapOpenAI and wrapAnthropic (buffered and streamed), the tool
    boundaries, authorizeForSink, the CLI's --restore, and the gateway. The
    gateway now restores streamed responses event by event and field by field, so
    a placeholder split across two events is put back and tool arguments that are
    JSON inside a JSON event are escaped at both levels. response.streamEscape: 'none' keeps the old byte-level behaviour.
  • OpenAI json_object/json_schema and Anthropic output_config.format
    requests have their streamed text restored escaped too.
  • The Python, Go and Rust engines follow the same rule, described in FRS-1
    section 11 and checked by new conformance cases. Python's wrap_openai and
    wrap_anthropic now restore streamed tool arguments (they were left as
    placeholders) and no longer drop text held back at the end of a field. Go and
    Rust add a JSON stream restorer (StreamJSON, stream_json) for callers that
    restore tool arguments themselves.
  • Known limits: JSON carried as a string inside tool arguments gets one level of
    escaping, and the deprecated streaming function_call is not restored.
Security: url_credentials in linear time (GHSA-x2x8-c4pf-r947)
  • The URL scheme in url_credentials is limited to 64 characters. Unbounded, a
    long run of scheme characters such as a-b.a-b.… made matching take time
    quadratic in its length: about 7 s for 80 kB through the default redact(),
    and the same in the Python engine. 1 MB now takes about 130 ms.
  • The scheme may contain _, so passwords in SQLAlchemy URLs such as
    oracle+cx_oracle://scott:tiger@db and redshift+redshift_connector://…
    are masked. They were not masked before.
  • Ships in the FRS-1 pack, which moves to version 1.10.0, with new conformance
    cases and a new case in npm run benchmark:adversarial.
Vercel AI SDK
  • Add flare-redact/ai-sdk. wrapLanguageModel({ model, middleware: flareRedactMiddleware() }) keeps secrets and personal data out of prompts for
    every provider the AI SDK supports (OpenAI, Anthropic, Google, Bedrock,
    Mistral, Groq and the rest). System, user and assistant text, reasoning,
    tool-call inputs and tool results become placeholders before the call; text,
    reasoning, tool calls and structured output are restored after it, streamed or
    not, including placeholders split across chunks. Files and images pass through
    unchanged.
  • It takes the same options as wrapOpenAI, plus session to keep placeholders
    stable across calls, and works with AI SDK 5, 6 and 7 without depending on
    ai. flare-redact init recognises the ai package and prints the line.
39 more detectors (90 to 129)
  • 25 service tokens, on by default: aws_bedrock_key, langsmith_key,
    pinecone_key, tavily_key, pypi_token, rubygems_key,
    dockerhub_token, jfrog_token, google_oauth_secret,
    alibaba_access_key, heroku_api_key, flyio_token,
    terraform_cloud_token, pulumi_token, planetscale_token,
    onepassword_token, age_secret_key, sentry_auth_token, grafana_token,
    dynatrace_token, atlassian_token, slack_webhook, mailchimp_key,
    brevo_key and resend_key.
  • gitlab_token catches GitLab 17's longer personal access tokens and the
    deploy, runner, trigger, CI job and other GitLab token types.
    digitalocean_token catches OAuth (doo_v1_) and refresh (dor_v1_) tokens.
  • 14 national IDs, off by default and reached through enable or the llm,
    gdpr and strict presets, each validated by its check digit and, where the
    number carries one, its birth date: ro_cnp, se_personnummer, fi_hetu,
    no_fodselsnummer, be_national_number, pt_nif, za_id, mx_curp,
    cl_rut, ar_cuit, sg_nric, il_teudat_zehut, gr_amka and uk_nino
    (prefix and suffix rules; it has no check digit). With za or ro enabled, a
    South African ID or Romanian CNP is masked whole instead of as a card number.
  • Every detector ships in all four engines through the FRS-1 pack, with match
    and near-miss tests and hostile-input cases in the adversarial benchmark.
Where people already look
  • Add .pre-commit-hooks.yaml: id: flare-redact stops a commit for the lines
    it adds, and id: flare-redact-files scans whole files for
    pre-commit run --all-files and pre-commit.ci. The package now builds in
    prepack, so installing it from a git checkout works.
  • Add a GitHub Action: uses: flare-collection/flare-redact@v1 scans the
    checkout, annotates each finding on the pull request, writes a job summary,
    can upload SARIF to code scanning, and never prints a value. Each release
    moves the v1 tag.
  • The Python and Rust engines are published to PyPI and crates.io from this
    release on, and the Go module gets sdk/go/vX.Y.Z tags so go get sees real
    versions. Both packages now include the licence file.
Platforms
  • CI runs the whole suite on Windows and macOS. --scan reports file paths with
    forward slashes on every platform; on Windows they used backslashes, which also
    made SARIF URIs invalid there.
  • The Python engine requires 3.9 or newer, the oldest version CI tests.

v1.9.1

Compare Source

Documentation
  • The README is now a short overview: what it does, a quick start, where it
    plugs in (logs, LLM prompts, Sentry, commits), how it compares with logger
    path redaction, Sentry scrubbing, gitleaks and Presidio, and an FAQ.
  • The complete documentation moved, unchanged, to
    docs/guide.md, which also ships in the npm package so
    coding assistants reading node_modules find it.
  • Tests check that every README link lands on a real heading in the guide and
    that every detector count matches the code.

No code changes.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8404570

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/flare-redact-1.x branch from 9221b37 to a49d44c Compare November 18, 2026 14:26
@renovate renovate Bot changed the title fix(deps): update dependency flare-redact to v1.9.1 fix(deps): update dependency flare-redact to v1.10.0 Nov 18, 2026
@renovate
renovate Bot force-pushed the renovate/flare-redact-1.x branch from a49d44c to f4f681d Compare November 19, 2026 12:06
@renovate renovate Bot changed the title fix(deps): update dependency flare-redact to v1.10.0 fix(deps): update dependency flare-redact to v1.10.1 Nov 19, 2026
@renovate
renovate Bot force-pushed the renovate/flare-redact-1.x branch from f4f681d to 8404570 Compare November 20, 2026 11:02
@renovate renovate Bot changed the title fix(deps): update dependency flare-redact to v1.10.1 fix(deps): update dependency flare-redact to v1.10.2 Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants