← Home

@everymatrix/casino-coinroyale-list

100
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releaserayiispmariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstefan.vladgoe.sutadarie.tisaianustefanaotong.woodtikarncatalinpoclidcristi.ungureanumaria.bumbar1liviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:components/CasinoCoinroyaleList-DYGS9nvz.js AI (source-diff): Bundled/minified build output, not true obfuscation. ai
source-diff obfuscated-file:components/CasinoCoinroyaleList-BApFNtDd.cjs AI (source-diff): Bundled/minified build output, not true obfuscation. ai
source-diff obfuscated-file:components/CasinoCoinroyaleList-D-pCRNfq.js AI (source-diff): Bundled/minified build output, not true obfuscation. ai
maintainer-change maintainer-removed AI (maintainer-change): Internal org maintainer rotation across many EveryMatrix packages. ai
maintainer-change maintainer-added AI (maintainer-change): Internal org maintainer rotation across many EveryMatrix packages. ai
source-diff obfuscated-file:components/CasinoCoinroyaleList-D0n8ZPX5.js AI (source-diff): Standard Vite/Svelte minified bundle output; consistent with this package's established build pattern. ai
source-diff obfuscated-file:components/CasinoCoinroyaleList-Cy9M3h57.cjs AI (source-diff): Standard Vite/Svelte minified bundle output; consistent with this package's established build pattern. ai
source-diff obfuscated-file:components/CasinoCoinroyaleList-62f7ZBdu.js AI (source-diff): Standard Vite/Svelte minified bundle output; consistent with this package's established build pattern. ai
bogus-package bogus-package AI (bogus-package): Internal EveryMatrix widget component; no description/repo/deps is normal for this package family. ai
provenance no-provenance AI (provenance): No provenance across all versions; internal org package published via JFrog Artifactory. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this internal component package. ai

Versions (showing 100 of 332)

Version Deps Published
1.87.10 0 / 0
1.87.9 0 / 0
1.87.8 0 / 0
1.87.7 0 / 0
1.87.6 0 / 0
1.87.5 0 / 0
1.87.4 0 / 0
1.87.3 0 / 0
1.87.2 0 / 0
1.87.1 0 / 0
1.87.0 0 / 0
1.86.30 0 / 0
1.86.29 0 / 0
1.86.28 0 / 0
1.86.27 0 / 0
1.86.26 0 / 0
1.86.25 0 / 0
1.86.24 0 / 0
1.86.23 0 / 0
1.86.22 0 / 0
1.86.21 0 / 0
1.86.20 0 / 0
1.86.12 0 / 0
1.86.11 0 / 0
1.86.10 0 / 0
1.86.9 0 / 0
1.86.8 0 / 0
1.86.7 0 / 0
1.86.6 0 / 0
1.86.5 0 / 0
1.86.4 0 / 0
1.86.3 0 / 0
1.86.2 0 / 0
1.86.1 0 / 0
1.86.0 0 / 0
1.85.23 0 / 0
1.85.22 0 / 0
1.85.21 0 / 0
1.85.20 0 / 0
1.85.19 0 / 0
1.85.18 0 / 0
1.85.17 0 / 0
1.85.16 0 / 0
1.85.15 0 / 0
1.85.14 0 / 0
1.85.13 0 / 0
1.85.12 0 / 0
1.85.11 0 / 0
1.85.10 0 / 0
1.85.9 0 / 0
1.85.8 0 / 0
1.85.7 0 / 0
1.85.6 0 / 0
1.85.5 0 / 0
1.85.4 0 / 0
1.85.3 0 / 0
1.85.2 0 / 0
1.85.1 0 / 0
1.85.0 0 / 0
1.84.3 0 / 0
1.84.2 0 / 0
1.84.1 0 / 0
1.84.0 0 / 0
1.83.12 0 / 0
1.83.11 0 / 0
1.83.10 0 / 0
1.83.9 0 / 0
1.83.8 0 / 0
1.83.7 0 / 0
1.83.6 0 / 0
1.83.5 0 / 0
1.83.4 0 / 0
1.83.3 0 / 0
1.83.2 0 / 0
1.83.1 0 / 0
1.83.0 0 / 0
1.82.0 0 / 0
1.81.2 0 / 0
1.81.1 0 / 0
1.81.0 0 / 0
1.80.19 0 / 0
1.80.18 0 / 0
1.80.17 0 / 0
1.80.16 0 / 0
1.80.15 0 / 0
1.80.14 0 / 0
1.80.13 0 / 0
1.80.12 0 / 0
1.80.11 0 / 0
1.80.10 0 / 0
1.80.9 0 / 0
1.80.8 0 / 0
1.80.7 0 / 0
1.80.6 0 / 0
1.80.5 0 / 0
1.80.4 0 / 0
1.80.3 0 / 0
1.80.2 0 / 0
1.80.1 0 / 0
1.80.0 0 / 0
Showing 100 of 332 Next page →

v1.87.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.87.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.86.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.