Skip to content

chore(deps-dev): fix high-severity brace-expansion audit failure - #21

Merged
TheStreamCode merged 1 commit into
mainfrom
fix/audit-brace-expansion
Oct 14, 2026
Merged

TheStreamCode merged 1 commit into
mainfrom
fix/audit-brace-expansion

Conversation

@TheStreamCode

Copy link
Copy Markdown
Owner

Summary

Fixes the failing
pm audit gate on CI. The full-tree audit (
pm audit --audit-level=high) fails with 1 high-severity advisory on transitive �race-expansion 5.0.9 (GHSA-q2hr-2g5m-vwhr, GHSA-qhr7-859c-m2p7, GHSA-6j4f-fj2g-mc7p), reached via eslint -> minimatch -> brace-expansion.

Unblocks #19 and #20, which fail on the same gate for the same pre-existing reason.

Changes

  • package-lock.json: �race-expansion 5.0.9 -> 5.0.12 via
    pm audit fix (3 lines, no package.json change, no runtime code touched)

Testing

  • [x]
    pm run lint && npm test passes (178 pass, 0 fail, 2 skipped)
  • Tested on Windows
  • Tested on macOS / Linux (covered by the CI matrix)
  • Verified with at least one real provider (N/A: lockfile-only change, no runtime behavior affected)
  • [x]
    pm audit --audit-level=high and
    pm audit --omit=dev --audit-level=high both report 0 vulnerabilities

Checklist

  • PR is focused on a single concern
  • README.md updated if user-facing behavior changed (N/A: no behavior change)
  • No API keys or credentials in code or examples
  • New provider entries document the base URL, model behavior, and authentication requirements (N/A: no provider changes)
  • Credential environment names are registered and tested when authentication is required (N/A)

Notes

Bumps transitive brace-expansion 5.0.9 -> 5.0.12 via npm audit fix (chain: eslint -> minimatch -> brace-expansion). Unblocks the npm audit gate failing on CI.
@TheStreamCode
TheStreamCode merged commit b3bb20a into main Oct 14, 2026
9 checks passed
@TheStreamCode
TheStreamCode deleted the fix/audit-brace-expansion branch October 14, 2026 19:12
TheStreamCode added a commit that referenced this pull request Oct 14, 2026
…22)

## Summary

Discovery-only catalog: the built-in catalog ships provider endpoints
only, and model lists always come from live GET /models — no shipped
lists to go stale. The catalog is also pruned to coding-oriented
frontier providers.

Stacked on #21 (audit fix): merge #21 first, then rebase this branch.

## Changes

- Removed all shipped model lists; fallback chain is now remembered list
-> pinned models -> provider omitted with a logged reason
- Ranking no longer prefers any model family (recency, version, context,
name)
- Vision flag is read from live provider metadata, like reasoning
already was
- Added muse (Meta Muse) and 
im (NVIDIA NIM) providers
- Removed stepfun, doubao, hunyuan, qianfan (**breaking**: configs
referencing these ids need updating)
- catalog:update is offline (no models.dev fetch); catalog:audit checks
each provider serves a usable chat model
- --no-discovery is now an offline mode (pinned or remembered lists, no
network)
- --list-providers shows key state and pinned/remembered counts
- New provider key envs registered in DEFAULT_SECRET_SOURCE_ENV and
covered by tests
- Docs: README, provider-verification (re-probed 2026-10-14),
troubleshooting, AGENTS.md, CHANGELOG, example config

## Testing

- [x] 
pm run lint && npm test passes (183 pass, 0 fail, 2 skipped; was
178/0/2)
- [x] Tested on Windows
- [ ] Tested on macOS / Linux (covered by the CI matrix)
- [x] Verified with real providers: catalog:audit live (7 keyless
catalogs resolve, incl. NIM 80/69 and OpenRouter 462/447); end-to-end
discovery+picker smoke against NIM (ids-only defaults) and OpenRouter
(real limits + vision flag)
- [x] 
pm pack --dry-run shows only shipped paths; both 
pm audit gates clean

## Checklist

- [x] PR is focused on a single concern
- [x] README.md updated if user-facing behavior changed
- [x] No API keys or credentials in code or examples
- [x] New provider entries document the base URL, model behavior, and
authentication requirements
- [x] Credential environment names are registered and tested when
authentication is required

## Notes

- muse/
im endpoints verified by probe (401 on invalid key) plus official docs
(Context7: Tencent/NVIDIA/Perplexity lookups during review; Meta has no
indexed API docs, so Muse rests on probes + convergent third-party
reports). No-key end-to-end inference run yet — keys needed.
- Perplexity, Baichuan, Baseten evaluated and deliberately not shipped
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.

1 participant