@zuzjs/flare
Official JavaScript/TypeScript client for ZuzFlare Server - Self-hosted real-time database
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/index-18tMqAtM.d.cts | AI (source-diff): TypeScript declaration file with readable JSDoc comments; long lines are bundled type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-18tMqAtM.d.ts | AI (source-diff): Same as .d.cts — bundled TS declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-Y0Mq_6P9.d.cts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-Y0Mq_6P9.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-DlQgWDy-.d.cts | AI (source-diff): TypeScript declaration file with long lines from bundled type defs; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-DlQgWDy-.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type defs; not obfuscated code. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.2.23 | 4 / 0 | |
| 0.2.22 | 4 / 0 | |
| 0.2.21 | 4 / 0 | |
| 0.2.20 | 4 / 0 | |
| 0.2.19 | 4 / 0 | |
| 0.2.18 | 4 / 0 | |
| 0.2.17 | 4 / 0 | |
| 0.2.16 | 4 / 0 | |
| 0.2.15 | 2 / 0 | |
| 0.2.14 | 2 / 0 | |
| 0.2.13 | 2 / 0 | |
| 0.2.12 | 2 / 0 | |
| 0.2.11 | 2 / 0 | |
| 0.2.10 | 2 / 0 | |
| 0.2.9 | 2 / 0 | |
| 0.2.8 | 2 / 0 | |
| 0.2.7 | 2 / 0 | |
| 0.2.6 | 2 / 0 | |
| 0.2.5 | 2 / 0 | |
| 0.2.4 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 |
v0.2.23
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.22
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.21
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.20
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.19
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.18
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.