@everymatrix/user-funds-acknowledgment
Supply chain provenance
Status for the latest visible version.
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
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 | |
| 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 | |
| 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 | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @everymatrix component packages; not a malware indicator here. | ai |
Versions (showing 51 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.4.81 | 0 / 0 | |
| 0.4.80 | 0 / 0 | |
| 0.4.79 | 0 / 0 | |
| 0.4.78 | 0 / 0 | |
| 0.4.77 | 0 / 0 | |
| 0.4.76 | 0 / 0 | |
| 0.4.75 | 0 / 0 | |
| 0.4.74 | 0 / 0 | |
| 0.4.73 | 0 / 0 | |
| 0.4.72 | 0 / 0 | |
| 0.4.71 | 0 / 0 | |
| 0.4.70 | 0 / 0 | |
| 0.4.69 | 0 / 0 | |
| 0.4.68 | 0 / 0 | |
| 0.4.67 | 0 / 0 | |
| 0.4.66 | 0 / 0 | |
| 0.4.65 | 0 / 0 | |
| 0.4.64 | 0 / 0 | |
| 0.4.63 | 0 / 0 | |
| 0.4.62 | 0 / 0 | |
| 0.4.61 | 0 / 0 | |
| 0.4.60 | 0 / 0 | |
| 0.4.59 | 0 / 0 | |
| 0.4.58 | 0 / 0 | |
| 0.4.57 | 0 / 0 | |
| 0.4.56 | 0 / 0 | |
| 0.4.55 | 0 / 0 | |
| 0.4.54 | 0 / 0 | |
| 0.4.53 | 0 / 0 | |
| 0.4.52 | 0 / 0 | |
| 0.4.51 | 0 / 0 | |
| 0.4.50 | 0 / 0 | |
| 0.4.49 | 0 / 0 | |
| 0.4.48 | 0 / 0 | |
| 0.4.47 | 0 / 0 | |
| 0.4.46 | 0 / 0 | |
| 0.4.45 | 0 / 0 | |
| 0.4.44 | 0 / 0 | |
| 0.4.43 | 0 / 0 | |
| 0.4.42 | 0 / 0 | |
| 0.4.41 | 0 / 0 | |
| 0.4.40 | 0 / 0 | |
| 0.4.39 | 0 / 0 | |
| 0.4.38 | 0 / 0 | |
| 0.4.37 | 0 / 0 | |
| 0.4.36 | 0 / 0 | |
| 0.4.35 | 0 / 0 | |
| 0.4.34 | 0 / 0 | |
| 0.4.33 | 0 / 0 | |
| 0.4.32 | 0 / 0 | |
| 0.4.31 | 0 / 0 |
v0.4.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.