Daily security sweep — backlog

Running list of Dependabot alerts that the routine dependency sweep cannot close, with the reason and a proposed path for each. Updated as the sweep runs.

No local check failed in this batch — nothing here is a build or test failure. Every item below is blocked on an upstream release or on a parent package's pin.

Blocked: no fixed release exists upstream

For these, the advisory's affected range extends through the latest published version, so there is nothing to bump to. Verified against the registry, not just Dependabot's first_patched_version field. These should be left open so they close automatically when a fix ships — dismissing them would suppress that.

Alert	Sev	Package	Lockfile	Latest published	Advisory range
#1410	critical	chromadb	hindsight-integrations/crewai/uv.lock	1.5.9	>=0.4.17, <=1.5.9
#1409	high	chromadb	hindsight-integrations/crewai/uv.lock	1.5.9	>=0.4.17, <=1.5.9
#1408	high	chromadb	hindsight-integrations/crewai/uv.lock	1.5.9	>=0.5.0, <=1.5.9
#1432	high	nltk	hindsight-integrations/llamaindex/uv.lock	3.10.3	<=3.10.3
#1431	high	nltk	hindsight-integrations/pipecat/uv.lock	3.10.3	<=3.10.3
#1381	high	image-size	package-lock.json	2.0.2	<=2.0.2
#1380	high	image-size	package-lock.json	2.0.2	<=2.0.2
#1382	low	elliptic	hindsight-integrations/eliza/package-lock.json	6.6.1	<=6.6.1
#102	medium	diskcache	uv.lock	5.6.3	<=5.6.3

Note on the nltk pair: these are successor advisories to the ones closed by the 3.10.3 bump. 3.10.3 is both the fix for the earlier advisories and the affected version for these two.

Note on chromadb: a parent bump does not help either. crewai pins chromadb~=1.1.0 at both the currently locked 1.6.1 and at 1.15.15, so moving crewai does not move chromadb out of range.

Path forward: poll upstream; these close on their own once a patched release lands.

Blocked: parent pin requires a code migration

#1032 — json-repair (high) — hindsight-integrations/crewai/uv.lock

Advisory: <0.60.1, fixed in 0.60.1. Locked at 0.25.2.

Not bumpable in isolation. Confirmed against the registry:

• crewai 1.6.1 (currently locked) declares json-repair==0.25.2 — an exact pin, so no override or scoped upgrade can move it.
• json-repair~=0.60.1 first appears at crewai 1.15.15.

Taking the fix therefore means crewai 1.6.1 → 1.15.x, which crosses the Storage → StorageBackend rename. hindsight-integrations/crewai/hindsight_crewai/storage.py subclasses the interface directly (class HindsightStorage(Storage) importing from crewai.memory.storage.interface), so this is a code migration, not a dependency bump.

Path forward: schedule as its own change — port HindsightStorage to the new base class, bump crewai, then re-lock. Should not be attempted inside a routine dependency sweep.

#1028 — agno (high) — hindsight-integrations/agno/uv.lock

SQL injection advisory, range <=2.6.5, and Dependabot reports no patched version. However the registry's latest agno is 3.0.5, which sits outside the affected range — so a major upgrade is likely the actual remedy even though the advisory does not name one.

Path forward: evaluate agno 2.x → 3.x as a deliberate change, checking the integration against the 3.x API surface. Not a mechanical bump, so it was left out of the routine batch.