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

@lincyaw/workbench@0.2.0-rc.2

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 source implements user-directed transcription editing, and the inspected network client targets the workbench API. Telemetry is disclosed in source and sends only after the host enables collection; no malicious behavior was found.

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

Consumers import the exported components; user actions invoke workbench operations. Telemetry starts through the workbench and remains disabled unless the host reports it enabled.

Impact

No malicious impact identified; ordinary workbench requests and host-enabled telemetry are the observed network behavior.

Mechanism

Workspace requests use the configured API base, which defaults to relative api/presmium/. Enabled telemetry batches UI operations to that host. Transcription edits are saved to browser localStorage and previewed only on user action.

AI rationale

Evidence

browser localStorage: presmium.transcription-draft.v1:*browser localStorage: presmium.telemetry.browser

Network endpoints2

api/presmium/api/presmium/telemetry

Decision evidence

public snapshot

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

Evidence for AI clean decision

The package exports its React workbench source entry points; package.json declares no lifecycle scripts or executable bin.
Transcription drafts are stored in browser localStorage under a workbench-specific key.
Transcription preview requires an explicit user action and checks that the authoring source is ready.
Telemetry sends operations to the same-origin workbench host only after that host reports collection is enabled.

Evidence against

The inspected network client uses the configurable workbench API base, defaulting to the relative path api/presmium/.
No credential collection, unrelated network destination, install-time action, or unsolicited account action was identified.

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 High2 Medium7 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

MediumStripped Provenance Metadatasrc/panels/TranscriptionAdoption.tsx

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.2.

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

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

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

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

@lincyaw/workbench@0.2.0-rc.2

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

Consumers import the exported components; user actions invoke workbench operations. Telemetry starts through the workbench and remains disabled unless the host reports it enabled.

Impact

No malicious impact identified; ordinary workbench requests and host-enabled telemetry are the observed network behavior.

Mechanism

AI rationale

Evidence

browser localStorage: presmium.transcription-draft.v1:*browser localStorage: presmium.telemetry.browser

Network endpoints2

api/presmium/api/presmium/telemetry

Decision evidence

public snapshot

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

Evidence for AI clean decision

The package exports its React workbench source entry points; package.json declares no lifecycle scripts or executable bin.
Transcription drafts are stored in browser localStorage under a workbench-specific key.
Transcription preview requires an explicit user action and checks that the authoring source is ready.
Telemetry sends operations to the same-origin workbench host only after that host reports collection is enabled.

Evidence against

The inspected network client uses the configurable workbench API base, defaulting to the relative path api/presmium/.
No credential collection, unrelated network destination, install-time action, or unsolicited account action was identified.

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 High2 Medium7 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

MediumStripped Provenance Metadatasrc/panels/TranscriptionAdoption.tsx

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.2.

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

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

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