registry / @lincyaw/workbench / 0.2.0-rc.12

@lincyaw/workbench@0.2.0-rc.12

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 flagged transcription panel implements a user-driven review and adoption flow, and package metadata shows no install lifecycle scripts. Runtime telemetry is sent to the same-origin host only when that host enables collection; the visible source does not show malicious behavior.

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

Telemetry starts when a Workbench is constructed and sends only if the host enables collection; transcription adoption requires user actions.

Impact

No unauthorized credential access, exfiltration, or account action was found. Enabled telemetry may include control labels and operation attributes such as document identifiers or file paths.

Mechanism

The package sends queued operation events to the same-origin /api/presmium/telemetry endpoint when enabled. Transcription changes are previewed and require explicit application.

AI rationale

Evidence

localStorage key presmium.telemetry.browserlocalStorage key presmium.transcription-draft.v1:<identity and transcription context>

Network endpoints1

/api/presmium/telemetry

Decision evidence

public snapshot

AI called this Clean at 86.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json declares module exports and no lifecycle scripts.
Transcription preview and adoption run from explicit UI actions; applying also requires a reviewed plan and confirmation.
Telemetry is sent only after the host reports it enabled, to the same-origin host endpoint.

Evidence against

When enabled, telemetry records control labels and operation attributes, which may include document identifiers or changed file paths.
The flagged TranscriptionAdoption.tsx source similarity was not independently explained by the visible source.

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 High1 Medium8 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

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencesrc/panels/TranscriptionAdoption.tsx

LowAi Review Evidencesrc/telemetry.ts

Affected versions and remediation

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

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

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.12 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:04:29.913Z (UTC).

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

registry / @lincyaw/workbench / 0.2.0-rc.12

@lincyaw/workbench@0.2.0-rc.12

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

Telemetry starts when a Workbench is constructed and sends only if the host enables collection; transcription adoption requires user actions.

Impact

No unauthorized credential access, exfiltration, or account action was found. Enabled telemetry may include control labels and operation attributes such as document identifiers or file paths.

Mechanism

The package sends queued operation events to the same-origin /api/presmium/telemetry endpoint when enabled. Transcription changes are previewed and require explicit application.

AI rationale

Evidence

localStorage key presmium.telemetry.browserlocalStorage key presmium.transcription-draft.v1:<identity and transcription context>

Network endpoints1

/api/presmium/telemetry

Decision evidence

public snapshot

AI called this Clean at 86.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json declares module exports and no lifecycle scripts.
Transcription preview and adoption run from explicit UI actions; applying also requires a reviewed plan and confirmation.
Telemetry is sent only after the host reports it enabled, to the same-origin host endpoint.

Evidence against

When enabled, telemetry records control labels and operation attributes, which may include document identifiers or changed file paths.
The flagged TranscriptionAdoption.tsx source similarity was not independently explained by the visible source.

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 High1 Medium8 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

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencesrc/panels/TranscriptionAdoption.tsx

LowAi Review Evidencesrc/telemetry.ts

Affected versions and remediation

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

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

Review the evidence and your use of @lincyaw/workbench@0.2.0-rc.12 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:04:29.913Z (UTC).

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