@everymatrix/general-logout
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/GeneralLogout-CGqV78za.js | AI (source-diff): Standard minified Svelte/Rollup bundle output; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/GeneralLogout-DDg9ndbc.cjs | AI (source-diff): Standard minified Svelte/Rollup bundle output; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/GeneralLogout-BtlGLI9p.js | AI (source-diff): Standard minified Svelte/Rollup bundle output; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/GeneralLogout-CQef-Jah.js | AI (source-diff): Standard Svelte/Vite minified bundle output; consistent pattern across all versions of this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralLogout-DsmMdpPL.cjs | AI (source-diff): Standard Svelte/Vite minified bundle output; consistent pattern across all versions of this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralLogout-IXsvPAN0.js | AI (source-diff): Standard Svelte/Vite minified bundle output; consistent pattern across all versions of this component library. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped component package; no deps/repo/description is consistent across all 993 versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance has been provided across this package's history; stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this internal component package across all versions. | ai |
Versions (showing 14 of 224)
| Version | Deps | Published |
|---|---|---|
| 1.71.1 | 0 / 0 | |
| 1.71.0 | 0 / 0 | |
| 1.70.1 | 0 / 0 | |
| 1.70.0 | 0 / 0 | |
| 1.69.3 | 0 / 0 | |
| 1.69.2 | 0 / 0 | |
| 1.69.0 | 0 / 0 | |
| 1.68.0 | 0 / 0 | |
| 1.67.3 | 0 / 0 | |
| 1.67.0 | 0 / 0 | |
| 1.66.2 | 0 / 0 | |
| 1.66.1 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.3 | 0 / 0 |
v1.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.