@animated-waffle/client@0.5.7
Framework-independent browser SDK for Narya Animated Waffle talking Agents.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThis version discloses automatic SDK version and runtime reporting to the connected Agent. The payload is limited and request-gated, but no opt-out is apparent, so this merits a warning rather than a block.
Static reason
No blocking static signals were detected.
Trigger
The application connects the client and the connected Agent requests SDK information over RPC.
Impact
The connected Agent learns limited SDK and runtime metadata; no user content or credentials are included in this response.
Mechanism
The registered RPC handler returns the package name, SDK/core version, and runtime environment.
AI rationale
This version discloses automatic SDK version and runtime reporting to the connected Agent. The payload is limited and request-gated, but no opt-out is apparent, so this merits a warning rather than a block.
Evidence
dist/index.jsCHANGELOG.md
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The changelog says SDK version and runtime environment are automatically reported to the connected Agent.
- After connection, the client registers an SDK-info RPC handler that returns metadata when the Agent requests it.
- The returned metadata is limited to package name, SDK/core version, and browser or unknown runtime environment.
- Session creation uses a caller-provided token callback and sends its token to the configured Narya API origin.
Evidence against
- The SDK-info response is gated on a connected Agent making an RPC request; it does not run at install or import time.
- The reported fields do not include credentials, transcripts, audio, device identifiers, or network addresses.
- The session token flow is documented as using a short-lived token from the caller’s callback.
Behavioral surface
Network
MinifiedUrlStrings
Source & flagged code
5 flaggedCHANGELOG.mdView file
1# Changelog
## 0.5.7
- Add per-reply clock calibration and matched RTP-frame receive/decoder/playback diagnostics; retain explicit unavailable results on unsupported runtimes.
## 0.5.6
- Automatically report the built SDK version and runtime environment to the connected Agent; custom session starters require no extra forwarding.
## 0
Medium
Ai Review Evidence
The changelog says SDK version and runtime environment are automatically reported to the connected Agent.
CHANGELOG.mdView on unpkg · L1dist/index.jsView file
60ateRoom(),de(this,"avatarLoad",t=>this.diagnosticState.update({avatar:t})),de(this,"avatarError",t=>this.diagnosticState.update({avatar:"error",error:t}))}createRoom(){let e=new ht({adaptiveStream:!0,dynacast:!0,audioCaptureDefaults:{voiceIsolation:!1,...this.options.audioCapture}});return e.registerRpcMethod(De,async t=>{if(e!==this.room||this.currentStatus==="disconnected"||this.currentStatus==="disconnecting"||e.remoteParticipants.get(t.callerIdentity)?.kind!==D.AGENT)throw new Error("Untrusted SDK information request.");return JSON.stringify(this.sdk
Medium
Ai Review Evidence
After connection, the client registers an SDK-info RPC handler that returns metadata when the Agent requests it.
dist/index.jsFindings
6 Medium1 Low
MediumNetwork
MediumAi Review EvidenceCHANGELOG.md
MediumAi Review Evidencedist/index.js
MediumAi Review Evidencedist/index.js
MediumAi Review Evidencedist/index.js
MediumAi Review EvidenceREADME.md
LowUrl Strings
Affected versions and remediation
This report applies to @animated-waffle/client@0.5.7.
See all versions of @animated-waffle/client for other recorded verdicts.
- Review the evidence and your use of @animated-waffle/client@0.5.7 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.