@everymatrix/player-elevate-level-jojogroup No license 29 versions

@everymatrix/player-elevate-level-jojogroup

npm

29

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releasemariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstrulea.sebastianstefan.vladgoe.sutadragos.bodeamaria.bumbarstefanaotong.woodtikarncatalinpoclidcristi.ungureanuliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/esm/player-elevate-card-items-19d02d44.js	AI (source-diff): Standard minified Stencil build output; samples show date-fns and locale utilities, not obfuscation.	ai	2026/04/30
source-diff	obfuscated-file:dist/cjs/player-elevate-card-items-d1fd2cc5.js	AI (source-diff): Standard minified CJS build artifact; same date-fns/locale content as ESM counterpart.	ai	2026/04/30
source-diff	obfuscated-file:dist/player-elevate-level-jojogroup/player-elevate-card-items-19d02d44.js	AI (source-diff): Minified Stencil dist output; content is date-fns utilities, not malicious obfuscation.	ai	2026/04/30
source-diff	obfuscated-file:dist/player-elevate-level-jojogroup/locale.utils-10bf5b6c.js	AI (source-diff): Long-line locale string map; minified but plainly readable i18n data, not obfuscated code.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Scoped everymatrix monorepo component; sparse metadata is a consistent pattern across all 205 versions, not a spam/malware signal.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Auto-generated component package in a large monorepo; missing description is a stable pattern for this publisher.	ai	2026/04/29

Versions (showing 29 of 131)

Version	Deps	Published
1.83.11	0 / 0	2025-11-06
1.83.10	0 / 0	2025-11-04
1.83.9	0 / 0	2025-11-03
1.83.8	0 / 0	2025-11-03
1.83.7	0 / 0	2025-11-03
1.83.6	0 / 0	2025-10-31
1.83.5	0 / 0	2025-10-31
1.83.4	0 / 0	2025-10-30
1.83.3	0 / 0	2025-10-30
1.83.2	0 / 0	2025-10-29
1.83.1	0 / 0	2025-10-29
1.83.0	0 / 0	2025-10-28
1.82.0	0 / 0	2025-10-28
1.81.2	0 / 0	2025-10-28
1.81.1	0 / 0	2025-10-28
1.81.0	0 / 0	2025-10-27
1.80.15	0 / 0	2025-10-27
1.80.14	0 / 0	2025-10-27
1.80.13	0 / 0	2025-10-24
1.80.12	0 / 0	2025-10-23
1.80.11	0 / 0	2025-10-22
1.80.10	0 / 0	2025-10-22
1.80.9	0 / 0	2025-10-21
1.80.8	0 / 0	2025-10-16
1.80.7	0 / 0	2025-10-15
1.80.6	0 / 0	2025-10-14
1.80.5	0 / 0	2025-10-14
1.80.4	0 / 0	2025-10-13
1.80.3	0 / 0	2025-10-10

v1.83.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.83.6

1 finding

LOW No provenance attestation provenance

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

v1.83.5

1 finding

LOW No provenance attestation provenance

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

v1.83.4

1 finding

LOW No provenance attestation provenance

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

v1.83.3

1 finding

LOW No provenance attestation provenance

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

v1.83.2

1 finding

LOW No provenance attestation provenance

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

v1.83.1

1 finding

LOW No provenance attestation provenance

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

v1.83.0

1 finding

LOW No provenance attestation provenance

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

v1.82.0

1 finding

LOW No provenance attestation provenance

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

v1.81.2

1 finding

LOW No provenance attestation provenance

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

v1.81.1

1 finding

LOW No provenance attestation provenance

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

v1.81.0

1 finding

LOW No provenance attestation provenance

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

v1.80.15

1 finding

LOW No provenance attestation provenance

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

v1.80.14

1 finding

LOW No provenance attestation provenance

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

v1.80.13

1 finding

LOW No provenance attestation provenance

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

v1.80.12

1 finding

LOW No provenance attestation provenance

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

v1.80.11

1 finding

LOW No provenance attestation provenance

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

v1.80.10

1 finding

LOW No provenance attestation provenance

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

v1.80.9

1 finding

LOW No provenance attestation provenance

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

v1.80.8

1 finding

LOW No provenance attestation provenance

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

v1.80.7

1 finding

LOW No provenance attestation provenance

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

v1.80.6

1 finding

LOW No provenance attestation provenance

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

v1.80.5

1 finding

LOW No provenance attestation provenance

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

v1.80.4

1 finding

LOW No provenance attestation provenance

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

v1.80.3

1 finding

LOW No provenance attestation provenance

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