← Home

webserial-core

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

danidoble

Keywords

webserialserialweb-serial-apitypescriptevent-drivenabstractparserarduinoembeddedusbhardware

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/demos/assets/demo-shared-DnvFynUr.js AI (source-diff): Standard Vite-minified demo bundle; content matches library's WebSerial/WebBluetooth functionality. ai
source-diff obfuscated-file:dist/demos/assets/web-bluetooth-VVwTClLx.js AI (source-diff): Vite-minified demo asset for Web Bluetooth demo; no malicious content. ai
source-diff obfuscated-file:dist/demos/assets/web-serial-CsBUUDvz.js AI (source-diff): Vite-minified demo asset for Web Serial demo; no malicious content. ai
source-diff obfuscated-file:dist/demos/assets/web-usb-D7sSHjku.js AI (source-diff): Vite-minified demo asset for Web USB demo; no malicious content. ai
source-diff obfuscated-file:dist/demos/assets/websocket-DREvCVt-.js AI (source-diff): Vite-minified demo asset for WebSocket demo; no malicious content. ai
source-diff obfuscated-file:dist/webserial-core.cjs AI (source-diff): Standard Vite/Rollup minified bundle; content is clearly WebSerial library logic, not obfuscated malware. ai

Versions (showing 11 of 11)

Version Deps Published
2.1.0 0 / 16
2.0.3 0 / 16
2.0.2 0 / 16
2.0.1 0 / 16
2.0.0 0 / 16
1.2.3 0 / 13
1.2.2 0 / 13
1.2.1 0 / 13
1.2.0 0 / 13
1.1.5 0 / 13
1.1.4 0 / 13

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

8 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: danidoble.

HIGH New obfuscated file: dist/demos/assets/demo-shared-DnvFynUr.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/demos/assets/web-bluetooth-VVwTClLx.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/demos/assets/web-serial-CsBUUDvz.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/demos/assets/web-usb-D7sSHjku.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/demos/assets/websocket-DREvCVt-.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/webserial-core.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: danidoble.

HIGH New obfuscated file: dist/webserial-core.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.