@elliemae/pui-app-bridge
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 | obfuscated-file:dist/public/js/emuiAppBridge.4c0a4243086e44e29d0b.js | AI (source-diff): Standard webpack minified bundle for this package; long lines are expected build output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/public/js/emuiAppBridge.4c0a4243086e44e29d0b.js | AI (source-diff): Network+exec pattern in a UMD browser bundle is normal for a micro-frontend bridge library; no dropper behavior evident. | ai | |
| source-diff | obfuscated-file:dist/public/js/emuiAppBridge.867faf89adac3f81299e.js | AI (source-diff): Standard webpack minified bundle for an established Elliemae micro-frontend lib; source map included. | ai | |
| source-diff | net-exec-file:dist/public/js/emuiAppBridge.867faf89adac3f81299e.js | AI (source-diff): Network+exec pattern is webpack module loader boilerplate, not dropper malware. | ai | |
| phantom-deps | phantom-dep:pubsub-js | AI (phantom-deps): pubsub-js is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.28.2 | 4 / 10 | |
| 2.28.1 | 4 / 10 | |
| 2.28.0 | 4 / 10 | |
| 2.25.3 | 4 / 10 | |
| 2.25.2 | 4 / 10 | |
| 2.25.1 | 4 / 10 | |
| 2.25.0 | 4 / 10 | |
| 2.24.0 | 4 / 10 | |
| 2.23.4 | 4 / 10 | |
| 2.22.3 | 4 / 10 | |
| 2.22.0 | 4 / 10 | |
| 2.21.4 | 4 / 10 | |
| 2.21.2 | 4 / 10 | |
| 2.19.2 | 4 / 9 | |
| 2.19.1 | 4 / 9 | |
| 2.18.1 | 4 / 9 | |
| 2.17.9 | 4 / 9 | |
| 2.17.8 | 4 / 9 | |
| 2.17.4 | 4 / 9 | |
| 2.17.2 | 4 / 9 | |
| 2.17.1 | 4 / 9 | |
| 2.17.0 | 4 / 9 | |
| 2.16.6 | 4 / 9 |
v2.28.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.