@everymatrix/cashier-confirm-modal
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:components/CashierConfirmModal-5QbXsvgo.cjs | AI (source-diff): Bundled Svelte/Rollup component build output, not real obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierConfirmModal-D1ixBq4A.cjs | AI (source-diff): Bundled/minified Svelte component output, not true obfuscation; no malicious behavior present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable false positive for this internal package family. | ai | |
| source-diff | obfuscated-file:components/CashierConfirmModal-BT6K4tsf.cjs | AI (source-diff): Minified Svelte/bundler output, not true obfuscation; no malicious behavior present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package metadata sparsity is stable/expected across this package's history. | ai |
Versions (showing 20 of 220)
| Version | Deps | Published |
|---|---|---|
| 1.47.0 | 0 / 0 | |
| 1.46.1 | 0 / 0 | |
| 1.46.0 | 0 / 0 | |
| 1.45.14 | 0 / 0 | |
| 1.45.13 | 0 / 0 | |
| 1.45.11 | 0 / 0 | |
| 1.45.10 | 0 / 0 | |
| 1.45.9 | 0 / 0 | |
| 1.45.8 | 0 / 0 | |
| 1.45.7 | 0 / 0 | |
| 1.45.6 | 0 / 0 | |
| 1.45.5 | 0 / 0 | |
| 1.45.4 | 0 / 0 | |
| 1.45.3 | 0 / 0 | |
| 1.45.2 | 0 / 0 | |
| 1.45.0 | 0 / 0 | |
| 1.0.72 | 0 / 0 | |
| 1.0.71 | 0 / 0 | |
| 1.0.70 | 0 / 0 | |
| 1.0.69 | 0 / 0 |
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.