@everymatrix/user-funds-acknowledgment No license 51 versions

@everymatrix/user-funds-acknowledgment

npm

51

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.woodtikarncatalinpoclidliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/user-funds-acknowledgment/user-funds-acknowledgment-581975b2.js	AI (source-diff): Standard minified Rollup/Vite bundle for a UI widget; content is readable gambling-disclosure HTML, not obfuscated malware.	ai	2026/04/30
source-diff	obfuscated-file:dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js	AI (source-diff): Standard minified Stencil/Rollup bundle output; no obfuscation or malicious payload present.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Scoped corporate component package; sparse metadata and tiny entry point are normal for this @everymatrix build pipeline.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Consistent pattern across @everymatrix component packages; not a malware indicator here.	ai	2026/04/29

Versions (showing 51 of 62)

View all versions

Version	Deps	Published
0.4.28	0 / 0	2026-06-04
0.4.27	0 / 0	2026-06-04
0.4.26	0 / 0	2026-06-04
0.4.25	0 / 0	2026-06-03
0.4.24	0 / 0	2026-06-02
0.4.23	0 / 0	2026-06-02
0.4.22	0 / 0	2026-06-01
0.4.21	0 / 0	2026-06-01
0.4.20	0 / 0	2026-05-29
0.4.19	0 / 0	2026-05-28
0.4.18	0 / 0	2026-05-28
0.4.17	0 / 0	2026-05-27
0.4.16	0 / 0	2026-05-26
0.4.15	0 / 0	2026-05-26
0.4.9	0 / 0	2026-05-19
0.4.8	0 / 0	2026-05-18
0.4.7	0 / 0	2026-05-15
0.4.6	0 / 0	2026-05-15
0.4.5	0 / 0	2026-05-15
0.4.4	0 / 0	2026-05-14
0.4.3	0 / 0	2026-05-13
0.4.2	0 / 0	2026-05-12
0.4.1	0 / 0	2026-05-11
0.4.0	0 / 0	2026-05-08
0.3.15	0 / 0	2026-05-08
0.3.14	0 / 0	2026-05-07
0.3.13	0 / 0	2026-05-07
0.3.12	0 / 0	2026-05-07
0.3.11	0 / 0	2026-05-06
0.3.10	0 / 0	2026-05-06
0.3.9	0 / 0	2026-05-05
0.3.8	0 / 0	2026-05-05
0.3.7	0 / 0	2026-05-04
0.3.6	0 / 0	2026-05-01
0.3.5	0 / 0	2026-04-30
0.3.4	0 / 0	2026-04-29
0.3.3	0 / 0	2026-04-28
0.3.2	0 / 0	2026-04-27
0.3.1	0 / 0	2026-04-27
0.3.0	0 / 0	2026-04-24
0.2.8	0 / 0	2026-04-24
0.2.7	0 / 0	2026-04-24
0.2.6	0 / 0	2026-04-23
0.2.5	0 / 0	2026-04-22
0.2.4	0 / 0	2026-04-22
0.2.3	0 / 0	2026-04-22
0.2.2	0 / 0	2026-04-20
0.2.1	0 / 0	2026-04-20
0.2.0	0 / 0	2026-04-17
0.1.2	0 / 0	2026-04-17
0.1.1	0 / 0	2026-04-16

v0.4.28

1 finding

LOW No provenance attestation provenance

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

v0.4.27

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.25

1 finding

LOW No provenance attestation provenance

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

v0.4.24

1 finding

LOW No provenance attestation provenance

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

v0.4.23

1 finding

LOW No provenance attestation provenance

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

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: adrian.pripon → goe.suta (on 2026-05-26, known maintainer) provenance

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.

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.15

1 finding

LOW No provenance attestation provenance

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

v0.3.14

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.2

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-581975b2.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.1

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-581975b2.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.0

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-581975b2.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.8

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.7

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.6

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.5

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.4

2 findings

HIGH New obfuscated file: dist/user-funds-acknowledgment/user-funds-acknowledgment-3bf8deec.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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