@gui-chat-plugin/weather
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/samples-Yf-D6ypn.cjs | AI (source-diff): Vite-bundled output with JMA area codes; long lines are minification artifacts, not obfuscation. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 1 / 14 | |
| 0.1.0 | 1 / 14 | |
| 0.0.2 | 1 / 13 | |
| 0.0.1 | 1 / 13 |
v0.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.