livereload-js
LiveReload JS client - auto reload browser on changes
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/livereload.min.js | AI (source-diff): livereload-js is a browser client that by design makes network connections to the LiveReload server and reloads pages. The minified dist file is a standard browserify+terser build artifact; network+exec is the product's core feature, not malware. | ai | |
| provenance | no-provenance | AI (provenance): Established 11+ year old package with 26 approved versions; lack of Sigstore provenance is acceptable for this package's history and trust level. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 0 / 16 | |
| 4.0.1 | 0 / 16 | |
| 4.0.0 | 0 / 16 | |
| 3.4.1 | 0 / 16 | |
| 3.4.0 | 0 / 16 | |
| 3.3.3 | 0 / 16 | |
| 3.3.2 | 0 / 16 | |
| 3.3.1 | 0 / 17 | |
| 3.3.0 | 0 / 17 | |
| 3.2.5 | 0 / 17 | |
| 3.2.4 | 0 / 17 | |
| 3.2.3 | 0 / 17 | |
| 3.2.2 | 0 / 17 | |
| 3.2.1 | 0 / 17 | |
| 3.2.0 | 0 / 17 | |
| 3.1.0 | 0 / 17 | |
| 3.0.2 | 0 / 17 | |
| 3.0.1 | 0 / 17 | |
| 3.0.0 | 0 / 17 | |
| 2.4.0 | 0 / 9 | |
| 2.3.0 | 0 / 8 | |
| 2.2.3 | 0 / 8 | |
| 2.2.2 | 0 / 8 | |
| 2.2.1 | 0 / 8 | |
| 2.2.0 | 0 / 8 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.