faye
Simple pub/sub messaging for the web
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file-transition:client/faye-browser.js | AI (source-diff): Webpack-bundled browser client; XHR+eval-shim are normal build output for this pub/sub lib. | ai | |
| source-diff | net-exec-file-transition:client/faye-browser-min.js | AI (source-diff): Minified webpack bundle of the browser client; same benign build artifact. | ai | |
| source-diff | net-exec-file:browser/faye-browser-min.js | AI (source-diff): Pub/sub transport bundle; network+eval are legit client code. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval in minified bundle; benign for this library. | ai | |
| source-diff | net-exec-file:browser/faye-browser.js | AI (source-diff): Unminified browser transport source; expected network usage. | ai | |
| source-diff | obfuscated-file:browser/faye-browser-min.js | AI (source-diff): Minified browser build output from wake config, not obfuscation. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() usage is in a minified browser bundle (faye-browser-min.js), a standard webpack/bundler pattern. Not indicative of malicious behavior for this package. | ai | |
| provenance | no-provenance | AI (provenance): Faye is a long-established package (5605 days old) from a trusted publisher; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 6 / 7 | |
| 1.4.0 | 6 / 7 | |
| 1.3.0 | 6 / 7 | |
| 1.2.5 | 5 / 7 | |
| 1.2.4 | 5 / 7 | |
| 1.2.3 | 5 / 7 | |
| 1.2.2 | 5 / 7 | |
| 1.2.1 | 5 / 7 | |
| 1.2.0 | 5 / 7 | |
| 1.1.3 | 4 / 5 | |
| 1.1.2 | 4 / 5 | |
| 1.1.1 | 4 / 5 | |
| 1.1.0 | 4 / 5 | |
| 1.0.4 | 4 / 4 | |
| 1.0.3 | 4 / 4 | |
| 1.0.1 | 4 / 4 | |
| 1.0.0 | 3 / 4 |
v1.4.0
3 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
3 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
3 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.