@zayne-labs/eslint-config
Zayne Labs' ESLint config preset
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-DkgX1yNh.d.ts | AI (source-diff): Generated TypeScript declaration file from eslint-typegen; long lines are dense type unions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-DkgX1yNh.d.ts | AI (source-diff): False positive on .d.ts type declaration file; no runtime network or exec calls present. | ai | |
| source-diff | net-exec-file:dist/index-D_rhwt8F.d.ts | AI (source-diff): False positive on .d.ts type declaration file; no runtime network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-D_rhwt8F.d.ts | AI (source-diff): Generated TypeScript declaration file from eslint-typegen; long lines are rule type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-CInLgm8D.d.ts | AI (source-diff): Generated TypeScript declaration file from eslint-typegen; long lines are normal for bundled .d.ts output. | ai | |
| source-diff | net-exec-file:dist/index-CInLgm8D.d.ts | AI (source-diff): False positive on .d.ts file; type imports are not network calls or code execution. | ai | |
| source-diff | net-exec-file:dist/index-DAz17cHA.d.ts | AI (source-diff): False positive on a TypeScript declaration file; no actual network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-DAz17cHA.d.ts | AI (source-diff): Large .d.ts generated by eslint-typegen; long lines are type definitions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-COjQw2qB.d.ts | AI (source-diff): 880KB .d.ts typegen file with long lines from ESLint rule type unions; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-COjQw2qB.d.ts | AI (source-diff): False positive on a TypeScript declaration file; no network or exec calls present. | ai | |
| source-diff | net-exec-file:dist/index-Di_9jXRR.d.ts | AI (source-diff): False positive on a .d.ts type declaration file; no runtime network or code execution possible. | ai | |
| source-diff | obfuscated-file:dist/index-Di_9jXRR.d.ts | AI (source-diff): Generated .d.ts typegen output; long lines are normal for comprehensive ESLint rule type definitions. | ai | |
| source-diff | net-exec-file:dist/index-CX62ZwUi.d.ts | AI (source-diff): False positive on generated TypeScript declaration file; no actual network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-CX62ZwUi.d.ts | AI (source-diff): 812KB .d.ts file is eslint-typegen output with long lines from type definitions, not obfuscated code. | ai | |
| source-diff | net-exec-file:dist/index-B9fyLEo8.d.ts | AI (source-diff): False positive on a .d.ts type declaration file; no runtime network or exec calls possible in type-only files. | ai | |
| source-diff | obfuscated-file:dist/index-B9fyLEo8.d.ts | AI (source-diff): Generated TypeScript declaration file from eslint-typegen; long lines are normal for bundled .d.ts output. | ai | |
| source-diff | obfuscated-file:dist/index-D1Wqlq07.d.ts | AI (source-diff): Large generated TypeScript declaration file from eslint-typegen; long lines are rule type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-D1Wqlq07.d.ts | AI (source-diff): False positive on generated .d.ts file; no actual network calls or code execution present. | ai | |
| source-diff | obfuscated-file:dist/index-lbvapg8f.d.ts | AI (source-diff): 807KB .d.ts generated by eslint-typegen; long lines are type definitions, not obfuscated code. | ai | |
| source-diff | net-exec-file:dist/index-lbvapg8f.d.ts | AI (source-diff): False positive on generated TypeScript declaration file; no actual network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-H4NJ8Uyl.d.ts | AI (source-diff): 879KB .d.ts file with bundled ESLint rule type declarations; long lines are type signatures, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-H4NJ8Uyl.d.ts | AI (source-diff): TypeScript declaration file; no actual network calls or code execution, only type imports. | ai | |
| source-diff | net-exec-file:dist/index-BCpY0GFi.d.ts | AI (source-diff): False positive on generated type declaration file; no actual network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-BCpY0GFi.d.ts | AI (source-diff): Generated .d.ts from eslint-typegen; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-B8a2EaF4.d.ts | AI (source-diff): 885KB .d.ts file is a generated ESLint rule type bundle; long lines are type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-B8a2EaF4.d.ts | AI (source-diff): False positive on a .d.ts type declaration file; no actual network or code execution present. | ai | |
| source-diff | net-exec-file:dist/index-D2ucqYld.d.ts | AI (source-diff): False positive on .d.ts typegen file; no actual network calls or code execution present. | ai | |
| source-diff | obfuscated-file:dist/index-D2ucqYld.d.ts | AI (source-diff): Large generated TypeScript declaration file (typegen output); long lines are ESLint rule type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-BHP9DnyA.d.ts | AI (source-diff): False positive on generated TypeScript declaration file; no actual network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-BHP9DnyA.d.ts | AI (source-diff): 826KB .d.ts file is generated by eslint-typegen; long lines are type declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-CbECj6Pq.d.ts | AI (source-diff): Generated TypeScript declaration file from eslint-typegen; long lines are normal for bundled type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-CbECj6Pq.d.ts | AI (source-diff): .d.ts files contain only type declarations; any apparent network/exec patterns are false positives from type-level ESLint rule definitions. | ai | |
| source-diff | obfuscated-file:dist/index-Cv861ahS.d.ts | AI (source-diff): Large .d.ts is generated ESLint rule typegen output; long lines are normal for bundled TypeScript declarations. | ai | |
| source-diff | net-exec-file:dist/index-Cv861ahS.d.ts | AI (source-diff): False positive on a .d.ts declaration file; no runtime network or code execution possible in type-only files. | ai | |
| source-diff | obfuscated-file:dist/index-CmvCZvcc.d.ts | AI (source-diff): Large .d.ts file generated by eslint-typegen; long lines are type definitions, not obfuscated code. | ai | |
| source-diff | net-exec-file:dist/index-CmvCZvcc.d.ts | AI (source-diff): False positive on .d.ts typegen output; no actual network or exec calls present. | ai | |
| source-diff | net-exec-file:dist/index-0P4qj2JA.d.ts | AI (source-diff): False positive on a .d.ts type declaration file; no runtime network or exec calls present. | ai | |
| source-diff | obfuscated-file:dist/index-0P4qj2JA.d.ts | AI (source-diff): 828KB .d.ts is a bundled TypeScript declaration file from eslint-typegen; long lines are type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-2BT3Tfk-.d.ts | AI (source-diff): Type declaration file only; no runtime network or code execution possible in a .d.ts file. | ai | |
| source-diff | obfuscated-file:dist/index-2BT3Tfk-.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are expected in generated .d.ts output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-Bks1mRDk.d.ts | AI (source-diff): Generated .d.ts typegen file with long lines from concatenated JSDoc; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-Bks1mRDk.d.ts | AI (source-diff): False positive on a .d.ts declaration file; no runtime network or exec calls present. | ai | |
| source-diff | net-exec-file:dist/index-COPrhNGE.d.ts | AI (source-diff): False positive on .d.ts file; no actual network or code execution present, only type declarations. | ai | |
| source-diff | obfuscated-file:dist/index-COPrhNGE.d.ts | AI (source-diff): Large bundled .d.ts typegen output; long lines are ESLint rule type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-BnAUhIog.d.ts | AI (source-diff): False positive on a .d.ts type declaration file; no actual network or execution code present. | ai | |
| source-diff | obfuscated-file:dist/index-BnAUhIog.d.ts | AI (source-diff): 879KB .d.ts file contains bundled TypeScript type declarations with long lines — not obfuscation. | ai | |
| phantom-deps | phantom-dep:pnpm-workspace-yaml | AI (phantom-deps): Referenced in config files, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): Resolver referenced in config, not imported directly; expected ESLint config pattern. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): ESLint config preset; framework-scoped packages loaded by convention, not direct import. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 0.13.14 | 35 / 43 | |
| 0.13.13 | 35 / 43 | |
| 0.13.12 | 35 / 43 | |
| 0.13.11 | 35 / 43 | |
| 0.13.10 | 35 / 43 | |
| 0.13.9 | 35 / 43 | |
| 0.13.8 | 35 / 43 | |
| 0.13.7 | 35 / 43 | |
| 0.13.6 | 35 / 43 | |
| 0.13.5 | 35 / 43 | |
| 0.13.4 | 35 / 43 | |
| 0.13.2 | 35 / 43 | |
| 0.13.1 | 35 / 43 | |
| 0.13.0 | 35 / 43 | |
| 0.12.11 | 34 / 43 | |
| 0.12.10 | 34 / 44 | |
| 0.12.9 | 35 / 44 | |
| 0.12.8 | 35 / 44 | |
| 0.12.5 | 32 / 42 | |
| 0.12.4 | 31 / 40 | |
| 0.12.3 | 31 / 40 | |
| 0.12.2 | 31 / 40 | |
| 0.12.0 | 31 / 40 | |
| 0.11.31 | 31 / 40 | |
| 0.11.30 | 31 / 40 | |
| 0.11.29 | 31 / 40 | |
| 0.11.28 | 31 / 40 | |
| 0.11.27 | 31 / 40 | |
| 0.11.26 | 31 / 40 | |
| 0.11.25 | 31 / 40 | |
| 0.11.24 | 31 / 40 | |
| 0.11.23 | 31 / 40 | |
| 0.11.22 | 31 / 40 | |
| 0.11.21 | 32 / 39 | |
| 0.11.20 | 32 / 39 | |
| 0.11.19 | 31 / 40 | |
| 0.11.18 | 31 / 40 | |
| 0.11.17 | 31 / 40 | |
| 0.11.16 | 31 / 40 | |
| 0.11.15 | 31 / 40 | |
| 0.11.14 | 31 / 40 | |
| 0.11.13 | 31 / 40 | |
| 0.11.12 | 31 / 40 | |
| 0.11.11 | 31 / 40 | |
| 0.11.10 | 31 / 40 | |
| 0.11.9 | 31 / 40 | |
| 0.11.8 | 31 / 40 | |
| 0.11.7 | 31 / 40 | |
| 0.11.6 | 30 / 42 | |
| 0.11.5 | 30 / 41 | |
| 0.11.4 | 30 / 41 |
v0.13.14
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.13
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.12
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.11
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.10
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.9
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.8
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.7
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.5
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.11
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.10
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.31
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.30
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.29
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.28
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.27
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.26
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.25
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.24
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.17
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.16
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.15
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.