@everymatrix/lottery-oddsbom-ticket-bet
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/esm/lottery-oddsbom-ticket-bet-9d88b029.js | AI (source-diff): Standard minified Stencil/Vaadin component bundle; Vaadin license headers confirm legitimate build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-bf775447.js | AI (source-diff): CJS variant of the same minified Vaadin component bundle; legitimate build artifact. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-9d88b029.js | AI (source-diff): Same as above; customElements.define and fetch are expected in a web-component bundle. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-bf775447.js | AI (source-diff): CJS variant; same reasoning as ESM counterpart. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-9d88b029.js | AI (source-diff): Same minified Vaadin/Lit component bundle pattern; legitimate build artifact. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-9d88b029.js | AI (source-diff): Network calls and customElements.define are normal for a UI web-component library bundle. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-32060989.js | AI (source-diff): Benign fetch for CSS styling in a UI widget; no code execution concern. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-6aa76dcd.js | AI (source-diff): Benign fetch for CSS styling in a UI widget; no code execution concern. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-32060989.js | AI (source-diff): Benign fetch for CSS styling in a UI widget; no code execution concern. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-6aa76dcd.js | AI (source-diff): Standard minified StencilJS bundle output for this scoped widget. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-32060989.js | AI (source-diff): Standard minified StencilJS bundle output for this scoped widget. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-oddsbom-ticket-bet-32060989.js | AI (source-diff): Standard minified StencilJS bundle output for this scoped widget. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-be9e0618.js | AI (source-diff): Network calls are CSS URL fetches; dynamic code execution is innerHTML for styles — normal widget pattern. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-ca47341e.js | AI (source-diff): Same CSS fetch/inject pattern in CJS bundle; not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-ca47341e.js | AI (source-diff): CJS variant of the same minified Stencil build; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-oddsbom-ticket-bet-be9e0618.js | AI (source-diff): Standard Stencil.js minified build output; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-be9e0618.js | AI (source-diff): Same CSS fetch/inject pattern; not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-be9e0618.js | AI (source-diff): Same minified Stencil build artifact; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-71eb06e5.js | AI (source-diff): Same CSS-fetch + innerHTML pattern; not malicious for this widget package. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-oddsbom-ticket-bet-71eb06e5.js | AI (source-diff): Standard Stencil.js minified build output; consistent with entire @everymatrix widget portfolio. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-71eb06e5.js | AI (source-diff): Network calls are CSS URL fetches; dynamic code execution is innerHTML for styling — legitimate widget pattern. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-71eb06e5.js | AI (source-diff): Same minified Stencil.js bundle; stable false positive for this package family. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-7a5265c7.js | AI (source-diff): CJS variant of same minified Stencil.js build; stable false positive. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-7a5265c7.js | AI (source-diff): CJS variant; same CSS-fetch pattern, not a dropper. | ai | |
| source-diff | obfuscated-file:dist/cjs/helper-count-down_11.cjs.entry.js | AI (source-diff): Standard Stencil build output; minified but contains only UI component logic. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-683b4e39.js | AI (source-diff): CJS variant of same Stencil bundle; no malicious network/exec pattern. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-171ea491.js | AI (source-diff): Same as ESM variant; customElements.define + fetch for styling, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-171ea491.js | AI (source-diff): Network calls are fetch for translations/styling; dynamic execution is customElements.define — standard web component pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-683b4e39.js | AI (source-diff): Standard CJS Stencil build output with Vaadin license headers. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-171ea491.js | AI (source-diff): Minified Vaadin/Lit bundle; normal build artifact for this package family. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-oddsbom-ticket-bet-171ea491.js | AI (source-diff): Minified Vaadin/Lit bundle with Apache license headers; normal for this package family. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/helper-count-down_11.entry.js | AI (source-diff): Standard Stencil build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/esm/helper-count-down_11.entry.js | AI (source-diff): Standard Stencil ESM build output; no malicious patterns. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-oddsbom-ticket-bet-2da56108.js | AI (source-diff): Network calls are CSS URL fetches; dynamic code execution is innerHTML for styling — legitimate widget pattern. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-oddsbom-ticket-bet-4f14d2d1.js | AI (source-diff): Same CSS fetch/inject pattern in CJS format; legitimate widget behavior. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-oddsbom-ticket-bet-4f14d2d1.js | AI (source-diff): CJS variant of the same minified Stencil bundle; no malicious content. | ai | |
| source-diff | net-exec-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-2da56108.js | AI (source-diff): Same CSS fetch/inject pattern; legitimate widget behavior. | ai | |
| source-diff | obfuscated-file:dist/lottery-oddsbom-ticket-bet/lottery-oddsbom-ticket-bet-2da56108.js | AI (source-diff): Same minified Stencil bundle, different output target; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-oddsbom-ticket-bet-2da56108.js | AI (source-diff): Standard minified Stencil component bundle; pattern is consistent across all versions of this widget family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @everymatrix internal component packages; not a malware signal here. | ai | |
| provenance | no-provenance | AI (provenance): Internal corporate package; provenance not expected for this publisher pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Corporate widget library published to private JFrog registry; sparse metadata is a pattern across all @everymatrix packages. | ai |
Versions (showing 25 of 127)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.3 | 0 / 0 | |
| 0.4.2 | 0 / 0 | |
| 0.4.1 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.12 | 0 / 0 | |
| 0.3.11 | 0 / 0 | |
| 0.3.10 | 0 / 0 | |
| 0.3.9 | 0 / 0 | |
| 0.3.8 | 0 / 0 | |
| 0.3.7 | 0 / 0 | |
| 0.3.6 | 0 / 0 | |
| 0.3.5 | 0 / 0 | |
| 0.3.4 | 0 / 0 | |
| 0.3.3 | 0 / 0 | |
| 0.3.2 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.5.2
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
7 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 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 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.