browser-sync-client
Client-side scripts for BrowserSync
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mitt | AI (phantom-deps): Likely used in bundled webpack output; benign event-emitter lib, no scannable import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 3 / 15 | |
| 3.0.3 | 3 / 15 | |
| 3.0.2 | 3 / 15 | |
| 3.0.1 | 3 / 15 | |
| 3.0.0 | 3 / 15 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.