registry / Telemetry / @lincyaw/workbench / 0.2.0-rc.10

@lincyaw/workbench@0.2.0-rc.10

Presmium's workbench panels in React (the documents, a document edited on its rendered page with comments and version history) with the workspace service's client and the preview protocol's workbench side; @lincyaw/dsh places them in presmium studio (expe

AI Security Review

scanned 4d ago · by lpm-firewall-ai

This is not clearly malicious, but host-enabled runtime telemetry can transmit document and local file identifiers without an apparent user-facing consent or opt-out. The endpoint is relative to the host and no credential or content exfiltration was identified, so this warrants a warning rather than a publish block.

Static reason

No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

Workbench construction starts telemetry; data is recorded and sent when the host reports telemetry enabled.

Impact

The host operator can associate user interactions with document and local file names. No credentials or document contents were found in this flow.

Mechanism

The workbench collects click and operation metadata, including document identifiers and file paths, then sends JSON batches to its relative telemetry endpoint.

AI rationale

Evidence

src/telemetry.tssrc/workbench.tssrc/workspace-client.ts

Network endpoints1

same-origin api/presmium/telemetry

Decision evidence

public snapshot

AI called this Suspicious at 82.0% confidence as Unknown with medium false-positive risk.

Evidence for warning

Workbench creation starts operation telemetry automatically; it asks the host whether collection is enabled.
When enabled, click records include control labels, roles, activity tags and region labels.
Operation records can include the current document identifier and changed or revealed file paths.
Batches go to the relative api/presmium/telemetry endpoint; no unrelated collector or credential transfer was identified.

Evidence against

Telemetry is disabled unless the host reports enabled=true.
The flagged transcription component stores drafts locally and applies changes only after a review and explicit apply action.

Behavioral surface

Source

FilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 126 file(s), 1.23 MB of source, external domains: console.volcengine.com

Source & flagged code

8 flagged

src/places.ts#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

src/places.ts#virtual:normalized:round1View on unpkg

src/panels/TranscriptionAdoption.tsxView file

•matchType = normalized_sha256 matchedPackage = @lincyaw/workbench@0.2.0-rc.5 matchedPath = [redacted].tsx matchedIdentity = npm:QGxpbmN5YXcvd29ya2JlbmNo:0.2.0-rc.5 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

src/panels/TranscriptionAdoption.tsxView on unpkg

Findings

3 High6 Medium3 Low

HighSemantic Analysis Limitedsrc/places.ts#virtual:normalized:round1

HighKnown Malware Source Similaritysrc/panels/TranscriptionAdoption.tsx

HighKnown Malware Source Fingerprint Signaturesrc/panels/TranscriptionAdoption.tsx

MediumNetwork

MediumAi Review Evidencesrc/workbench.ts

MediumAi Review Evidencesrc/telemetry.ts

MediumAi Review Evidencesrc/workbench.ts

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @lincyaw/workbench@0.2.0-rc.10.

See all versions of @lincyaw/workbench for other recorded verdicts.

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.10 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: 2026-11-01 05:17:25.023Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / Telemetry / @lincyaw/workbench / 0.2.0-rc.10

@lincyaw/workbench@0.2.0-rc.10

AI Security Review

scanned 4d ago · by lpm-firewall-ai

Static reason

No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

Workbench construction starts telemetry; data is recorded and sent when the host reports telemetry enabled.

Impact

The host operator can associate user interactions with document and local file names. No credentials or document contents were found in this flow.

Mechanism

The workbench collects click and operation metadata, including document identifiers and file paths, then sends JSON batches to its relative telemetry endpoint.

AI rationale

Evidence

src/telemetry.tssrc/workbench.tssrc/workspace-client.ts

Network endpoints1

same-origin api/presmium/telemetry

Decision evidence

public snapshot

AI called this Suspicious at 82.0% confidence as Unknown with medium false-positive risk.

Evidence for warning

Workbench creation starts operation telemetry automatically; it asks the host whether collection is enabled.
When enabled, click records include control labels, roles, activity tags and region labels.
Operation records can include the current document identifier and changed or revealed file paths.
Batches go to the relative api/presmium/telemetry endpoint; no unrelated collector or credential transfer was identified.

Evidence against

Telemetry is disabled unless the host reports enabled=true.
The flagged transcription component stores drafts locally and applies changes only after a review and explicit apply action.

Behavioral surface

Source

FilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 126 file(s), 1.23 MB of source, external domains: console.volcengine.com

Source & flagged code

8 flagged

src/places.ts#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

src/places.ts#virtual:normalized:round1View on unpkg

src/panels/TranscriptionAdoption.tsxView file

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

src/panels/TranscriptionAdoption.tsxView on unpkg

Findings

3 High6 Medium3 Low

HighSemantic Analysis Limitedsrc/places.ts#virtual:normalized:round1

HighKnown Malware Source Similaritysrc/panels/TranscriptionAdoption.tsx

HighKnown Malware Source Fingerprint Signaturesrc/panels/TranscriptionAdoption.tsx

MediumNetwork

MediumAi Review Evidencesrc/workbench.ts

MediumAi Review Evidencesrc/telemetry.ts

MediumAi Review Evidencesrc/workbench.ts

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @lincyaw/workbench@0.2.0-rc.10.

See all versions of @lincyaw/workbench for other recorded verdicts.

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.10 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: 2026-11-01 05:17:25.023Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.