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

@lincyaw/workbench@0.2.0-rc.3

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

The package discloses host-controlled telemetry, but its records can contain document identifiers and local source paths. That identifying data makes this a warning-level telemetry concern rather than a clean result.

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 startup begins the logger; records are sent if the host reports telemetry enabled.

Impact

The host operator may associate user activity with local document identifiers and source paths.

Mechanism

The logger batches operation attributes and sends them to the same-origin `api/presmium/telemetry` endpoint.

AI rationale

Evidence

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

Network endpoints1

api/presmium/telemetry

Decision evidence

public snapshot

AI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

Workbench construction starts an operation logger, which asks the host whether collection is enabled.
Logged events can include the current document identifier and source paths, including file paths from changes and a path revealed by the user.
When enabled, batches are sent to the same-origin `api/presmium/telemetry` endpoint using `sendBeacon` or `fetch`.
The source describes this as telemetry for the operator’s collector and says the host controls whether it collects.

Evidence against

The manifest defines no lifecycle scripts; the package exports UI components and related workbench code.
Telemetry is gated on the host returning `enabled: true`; the flagged transcription flow sends its plan only after a user requests review and applies changes only after confirmation.

Behavioral surface

Source

FilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

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/workspace-client.ts

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

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

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

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.3 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 10:37:39.919Z (UTC).

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

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

@lincyaw/workbench@0.2.0-rc.3

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 startup begins the logger; records are sent if the host reports telemetry enabled.

Impact

The host operator may associate user activity with local document identifiers and source paths.

Mechanism

The logger batches operation attributes and sends them to the same-origin `api/presmium/telemetry` endpoint.

AI rationale

Evidence

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

Network endpoints1

api/presmium/telemetry

Decision evidence

public snapshot

AI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

Workbench construction starts an operation logger, which asks the host whether collection is enabled.
Logged events can include the current document identifier and source paths, including file paths from changes and a path revealed by the user.
When enabled, batches are sent to the same-origin `api/presmium/telemetry` endpoint using `sendBeacon` or `fetch`.
The source describes this as telemetry for the operator’s collector and says the host controls whether it collects.

Evidence against

The manifest defines no lifecycle scripts; the package exports UI components and related workbench code.
Telemetry is gated on the host returning `enabled: true`; the flagged transcription flow sends its plan only after a user requests review and applies changes only after confirmation.

Behavioral surface

Source

FilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

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/workspace-client.ts

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

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

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

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.3 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 10:37:39.919Z (UTC).

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