@everymatrix/lottery-tipping-entrance
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/lottery-tipping-entrance/lottery-tipping-entrance-f495c522.js | AI (source-diff): Network calls and dynamic code are part of the Vaadin/Lit web component framework bundle, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-f495c522.js | AI (source-diff): Standard Stencil/Vaadin bundler output; minified build artifact, not malicious obfuscation. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-tipping-entrance-f495c522.js | AI (source-diff): Network calls and dynamic code are part of the Vaadin/Lit web component framework bundle, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-tipping-entrance-f495c522.js | AI (source-diff): Standard Stencil/Vaadin bundler output; minified build artifact, not malicious obfuscation. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-tipping-entrance-f2feaebf.js | AI (source-diff): Network calls and dynamic code are part of the Vaadin/Lit web component framework bundle, not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-tipping-entrance-f2feaebf.js | AI (source-diff): Standard Stencil/Vaadin bundler output; minified build artifact, not malicious obfuscation. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-tipping-entrance-ded99035.js | AI (source-diff): Network calls and dynamic code (customElements.define) are normal web-component framework patterns, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-tipping-entrance-e50e77ae.js | AI (source-diff): Same web-component framework patterns; no exfiltration or shell execution present. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-tipping-entrance-e50e77ae.js | AI (source-diff): CJS build chunk; same Rollup minification pattern with Vaadin license headers. | ai | |
| source-diff | net-exec-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-ded99035.js | AI (source-diff): customElements.define and fetch are standard web-component APIs; not malicious. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-tipping-entrance-ded99035.js | AI (source-diff): Standard Rollup/Stencil minified build output with recognizable Vaadin/Lit license headers; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-ded99035.js | AI (source-diff): Same minified build artifact pattern; Vaadin/Lit license headers confirm legitimate framework code. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-762f3acc.js | AI (source-diff): Standard Stencil/Rollup minified build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/draw-selection_20.cjs.entry.js | AI (source-diff): Standard Stencil/Rollup minified build output; consistent pattern across all @everymatrix packages. | ai | |
| source-diff | obfuscated-file:dist/esm/draw-selection_20.entry.js | AI (source-diff): Standard Stencil/Rollup minified build output. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/draw-selection_20.entry.js | AI (source-diff): Standard Stencil/Rollup minified build output. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-tipping-entrance-762f3acc.js | AI (source-diff): Standard Stencil/Rollup minified build output; contains Vaadin/Lit license headers. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-tipping-entrance-d0c92753.js | AI (source-diff): Standard Stencil/Rollup minified build output. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-tipping-entrance-762f3acc.js | AI (source-diff): Network calls are fetch/XHR for widget data; dynamic code execution is customElements.define — normal web component pattern. | ai | |
| source-diff | net-exec-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-762f3acc.js | AI (source-diff): Same pattern: customElements.define + widget data fetch; not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-tipping-entrance-d0c92753.js | AI (source-diff): Same pattern: customElements.define + widget data fetch; not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/cjs/draw-selection_18.cjs.entry.js | AI (source-diff): Standard minified Stencil component build output; consistent with prior versions of this package. | ai | |
| source-diff | net-exec-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-76aac39c.js | AI (source-diff): Same Stencil runtime pattern; not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/esm/lottery-tipping-entrance-76aac39c.js | AI (source-diff): Same Stencil runtime pattern; not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/cjs/lottery-tipping-entrance-2f5e8ecd.js | AI (source-diff): Network calls and dynamic execution are part of Stencil/web-component runtime (fetch for styling, customElements.define); not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/lottery-tipping-entrance-76aac39c.js | AI (source-diff): Minified bundle with recognizable Vaadin/LitElement code and license headers; not malicious. | ai | |
| source-diff | obfuscated-file:dist/esm/lottery-tipping-entrance-76aac39c.js | AI (source-diff): Minified ESM bundle with recognizable library code and license headers; not malicious. | ai | |
| source-diff | obfuscated-file:dist/cjs/lottery-tipping-entrance-2f5e8ecd.js | AI (source-diff): Minified bundle with recognizable Vaadin/LitElement/date-fns code and license headers; not malicious. | ai | |
| source-diff | obfuscated-file:dist/lottery-tipping-entrance/draw-selection_18.entry.js | AI (source-diff): Standard minified Stencil build output; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/draw-selection_18.entry.js | AI (source-diff): Standard minified Stencil ESM build output; not obfuscation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with EveryMatrix's internal widget publishing pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Published from private JFrog registry; provenance attestation not expected for this org's pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Corporate scoped widget package with 251 versions; sparse metadata is a stable pattern for this org's auto-published components. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 1.94.34 | 0 / 0 | |
| 1.94.33 | 0 / 0 | |
| 1.94.32 | 0 / 0 | |
| 1.94.31 | 0 / 0 | |
| 1.94.30 | 0 / 0 | |
| 1.94.29 | 0 / 0 | |
| 1.94.28 | 0 / 0 | |
| 1.94.27 | 0 / 0 | |
| 1.94.26 | 0 / 0 | |
| 1.94.25 | 0 / 0 | |
| 1.94.24 | 0 / 0 | |
| 1.94.23 | 0 / 0 | |
| 1.94.22 | 0 / 0 | |
| 1.94.21 | 0 / 0 | |
| 1.94.20 | 0 / 0 | |
| 1.94.19 | 0 / 0 | |
| 1.94.18 | 0 / 0 | |
| 1.94.17 | 0 / 0 | |
| 1.94.16 | 0 / 0 | |
| 1.94.15 | 0 / 0 | |
| 1.94.9 | 0 / 0 | |
| 1.94.8 | 0 / 0 | |
| 1.94.7 | 0 / 0 | |
| 1.94.6 | 0 / 0 | |
| 1.94.5 | 0 / 0 | |
| 1.94.3 | 0 / 0 | |
| 1.94.2 | 0 / 0 | |
| 1.94.1 | 0 / 0 | |
| 1.94.0 | 0 / 0 | |
| 1.93.15 | 0 / 0 | |
| 1.93.14 | 0 / 0 | |
| 1.93.13 | 0 / 0 | |
| 1.93.12 | 0 / 0 | |
| 1.93.11 | 0 / 0 | |
| 1.93.10 | 0 / 0 | |
| 1.93.9 | 0 / 0 | |
| 1.93.8 | 0 / 0 | |
| 1.93.7 | 0 / 0 | |
| 1.93.6 | 0 / 0 | |
| 1.93.5 | 0 / 0 | |
| 1.93.4 | 0 / 0 | |
| 1.93.3 | 0 / 0 | |
| 1.93.2 | 0 / 0 | |
| 1.93.1 | 0 / 0 | |
| 1.93.0 | 0 / 0 | |
| 1.92.8 | 0 / 0 | |
| 1.92.7 | 0 / 0 | |
| 1.92.6 | 0 / 0 | |
| 1.92.5 | 0 / 0 | |
| 1.92.4 | 0 / 0 | |
| 1.92.3 | 0 / 0 |
v1.94.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-26, but goe.suta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.94.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.8
10 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
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.
v1.94.7
10 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
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.
v1.94.6
10 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
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.
v1.94.5
10 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
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.
v1.94.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.