@web/browser-logs
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
d4kmorpasslejorenbroekemabennyplarsdenbakkerwestbrookmodern-web
Keywords
webnodebrowserlogsserializationdeserializationserializedeserialize
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used only to create a named stub function for display; input is sanitized via regex replace, not arbitrary user input. | ai | |
| dependencies | unvetted-dep:errorstacks | AI (dependencies): errorstacks is a legitimate stack-trace parsing library; appropriate dependency for browser-logs deserialization. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 1 / 2 |
v0.4.1
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.