attocode-code-intel 0.1.0__py3-none-any.whl

attocode_intel/rules/packs/community/bandit-python/LICENSE

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS

attocode_intel/rules/packs/community/bandit-python/NOTICE

@@ -0,0 +1,13 @@
+# NOTICE — bandit-python
+
+Rule patterns adapted from Bandit (https://github.com/PyCQA/bandit). Original copyright PyCQA. Licensed under Apache-2.0.
+
+Upstream: https://github.com/PyCQA/bandit
+Commit:   (unspecified)
+License:  Apache-2.0
+
+Modifications:
+- Translated rule patterns to attocode UnifiedRule schema
+- Subset selection (high-value rules first)
+
+See LICENSE for full license terms.

attocode_intel/rules/packs/community/bandit-python/PORTING.md

@@ -0,0 +1,23 @@
+# Porting checklist — bandit-python
+
+Rules from bandit (https://github.com/PyCQA/bandit) are not YAML-defined upstream
+and require manual porting. Each ported rule MUST include the
+attribution comment header at the top of its YAML file:
+
+```yaml
+# Adapted from bandit rule '<original-id>'
+# See ../LICENSE and ../NOTICE for license terms.
+```
+
+Porting targets:
+
+- [ ] B105 hardcoded_password_string
+- [ ] B303 weak_md5_hash
+- [ ] B304 weak_des_cipher
+- [ ] B306 mktemp_temp_dir
+- [ ] B307 use_of_eval
+- [ ] B321 ftp_lib_used
+- [ ] B324 weak_sha1_hash
+- [ ] B501 request_with_no_cert_validation
+- [ ] B602 subprocess_with_shell_true
+- [ ] B608 hardcoded_sql_expressions

attocode_intel/rules/packs/community/bandit-python/manifest.yaml

@@ -0,0 +1,14 @@
+name: bandit-python
+version: 1.0.0
+languages:
+- python
+description: Hand-ported subset of bandit rules. See PORTING.md for the porting checklist.
+source: community
+source_url: https://github.com/PyCQA/bandit
+source_commit: ''
+source_license: Apache-2.0
+attribution: Rule patterns adapted from Bandit (https://github.com/PyCQA/bandit).
+  Original copyright PyCQA. Licensed under Apache-2.0.
+imported_at: '2026-04-16T12:20:09Z'
+upstream_rule_count: 10
+imported_rule_count: 0

attocode_intel/rules/packs/community/bandit-python/rules/B105-hardcoded-password.yaml

@@ -0,0 +1,23 @@
+# Adapted from bandit rule 'B105 hardcoded_password_string'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B105-hardcoded-password
+name: Hardcoded password string
+message: Possible hardcoded password assignment
+severity: high
+category: security
+languages: [python]
+confidence: 0.7
+cwe: CWE-798
+pattern: '(?i)\b(password|passwd|pwd|secret|token|api_key|apikey)\s*=\s*[''"][^''"]{3,}[''"]'
+explanation: |
+  Storing credentials in source code makes them easy to leak via version
+  control, logs, or stack traces. Bandit B105 catches the string-assignment
+  variant.
+recommendation: |
+  Move credentials to a secret manager (env vars, AWS Secrets Manager,
+  Vault) and read them at runtime. For tests, use clearly-non-credential
+  placeholders (e.g. ``"PLACEHOLDER"``).
+references:
+  - https://bandit.readthedocs.io/en/latest/plugins/b105_hardcoded_password_string.html
+  - https://cwe.mitre.org/data/definitions/798.html

attocode_intel/rules/packs/community/bandit-python/rules/B303-weak-md5.yaml

@@ -0,0 +1,21 @@
+# Adapted from bandit rule 'B303 weak_md5_hash'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B303-weak-md5
+name: Use of weak MD5 hash
+message: MD5 is cryptographically broken; use SHA-256 or stronger
+severity: high
+category: security
+languages: [python]
+confidence: 0.85
+cwe: CWE-327
+pattern: '\bhashlib\.md5\s*\('
+explanation: |
+  MD5 is vulnerable to collision attacks and is no longer considered
+  cryptographically secure. Bandit B303 flags any use as a security issue.
+recommendation: |
+  Use ``hashlib.sha256`` (or SHA-3) for cryptographic hashing. If the use
+  is non-security (e.g. cache key), pass ``usedforsecurity=False`` (Python 3.9+).
+references:
+  - https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html
+  - https://cwe.mitre.org/data/definitions/327.html

attocode_intel/rules/packs/community/bandit-python/rules/B304-weak-des.yaml

@@ -0,0 +1,20 @@
+# Adapted from bandit rule 'B304 weak_cipher'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B304-weak-des
+name: Use of weak DES cipher
+message: DES/3DES are cryptographically weak; use AES-GCM
+severity: high
+category: security
+languages: [python]
+confidence: 0.85
+cwe: CWE-327
+pattern: '\b(DES|TripleDES|ARC2|ARC4|Blowfish)\.new\s*\('
+explanation: |
+  DES has a 56-bit key (brute-forceable), 3DES is deprecated by NIST,
+  and RC4/RC2 have known biases. These ciphers should not be used.
+recommendation: |
+  Use AES-256-GCM via ``cryptography`` library
+  (``Cipher(algorithms.AES(key), modes.GCM(iv))``).
+references:
+  - https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html

attocode_intel/rules/packs/community/bandit-python/rules/B307-use-of-eval.yaml

@@ -0,0 +1,22 @@
+# Adapted from bandit rule 'B307 use_of_eval'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B307-use-of-eval
+name: Use of dynamic code evaluation
+message: Avoid eval/exec on dynamic input — leads to arbitrary code execution
+severity: critical
+category: security
+languages: [python]
+confidence: 0.8
+cwe: CWE-95
+pattern: '\b(eval|exec)\s*\('
+explanation: |
+  ``eval`` and ``exec`` interpret arbitrary strings as Python code. If any
+  part of the input is influenced by an external source, an attacker can
+  execute commands.
+recommendation: |
+  Use ``ast.literal_eval`` for trusted literal expressions, or a proper
+  parser/DSL for dynamic logic.
+references:
+  - https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html
+  - https://cwe.mitre.org/data/definitions/95.html

attocode_intel/rules/packs/community/bandit-python/rules/B324-weak-sha1.yaml

@@ -0,0 +1,21 @@
+# Adapted from bandit rule 'B324 weak_sha1_hash'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B324-weak-sha1
+name: Use of weak SHA-1 hash
+message: SHA-1 is cryptographically broken; use SHA-256 or stronger
+severity: high
+category: security
+languages: [python]
+confidence: 0.85
+cwe: CWE-327
+pattern: '\bhashlib\.sha1\s*\('
+explanation: |
+  SHA-1 has known collision attacks (SHAttered, 2017) and should not be
+  used for cryptographic purposes.
+recommendation: |
+  Use ``hashlib.sha256`` (or SHA-3). For non-security hashing such as
+  ETags or cache keys, pass ``usedforsecurity=False``.
+references:
+  - https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html
+  - https://cwe.mitre.org/data/definitions/327.html

attocode_intel/rules/packs/community/bandit-python/rules/B501-no-cert-validation.yaml

@@ -0,0 +1,23 @@
+# Adapted from bandit rule 'B501 request_with_no_cert_validation'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B501-no-cert-validation
+name: HTTPS request with TLS verification disabled
+message: TLS certificate verification disabled — vulnerable to MITM
+severity: high
+category: security
+languages: [python]
+confidence: 0.85
+cwe: CWE-295
+pattern: '\bverify\s*=\s*False\b'
+explanation: |
+  Setting ``verify=False`` on requests/httpx/urllib3 calls disables TLS
+  certificate validation. An attacker on the network can intercept,
+  read, or modify the traffic.
+recommendation: |
+  Leave verification enabled. If self-signed CAs are needed, point
+  ``verify`` at a CA bundle path (``verify="/path/to/ca.crt"``) rather
+  than disabling.
+references:
+  - https://bandit.readthedocs.io/en/latest/plugins/b501_request_with_no_cert_validation.html
+  - https://cwe.mitre.org/data/definitions/295.html

attocode_intel/rules/packs/community/bandit-python/rules/B602-shell-true.yaml

@@ -0,0 +1,22 @@
+# Adapted from bandit rule 'B602 subprocess_with_shell_true'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B602-shell-true
+name: Subprocess invoked with shell=True
+message: subprocess with shell=True is vulnerable to command injection
+severity: high
+category: security
+languages: [python]
+confidence: 0.8
+cwe: CWE-78
+pattern: '\bsubprocess\.\w+\([^)]*\bshell\s*=\s*True'
+explanation: |
+  ``subprocess.run/Popen/call`` with ``shell=True`` invokes the shell to
+  parse the command. If any argument comes from user input, the shell
+  will interpret meta-characters (``;``, ``|``, ``&&``, backticks).
+recommendation: |
+  Pass arguments as a list (``subprocess.run(["ls", "-la", path])``)
+  without ``shell=True``. The OS calls execve directly — no shell parsing.
+references:
+  - https://bandit.readthedocs.io/en/latest/plugins/b602_subprocess_popen_with_shell_equals_true.html
+  - https://cwe.mitre.org/data/definitions/78.html

attocode_intel/rules/packs/community/bandit-python/rules/B608-sqli.yaml

@@ -0,0 +1,22 @@
+# Adapted from bandit rule 'B608 hardcoded_sql_expressions'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: B608-sqli
+name: SQL string built via concatenation or f-string
+message: SQL string interpolation — possible injection
+severity: high
+category: security
+languages: [python]
+confidence: 0.6
+cwe: CWE-89
+pattern: '(SELECT|INSERT|UPDATE|DELETE)\s+[^;''"]*[''"]\s*[+%]\s*\w+'
+explanation: |
+  Building SQL by concatenating user input or formatting variables into
+  the query string is the classic SQL-injection pattern. The bandit
+  variant catches both ``+`` concatenation and ``%`` formatting.
+recommendation: |
+  Use parameterized queries (``cursor.execute(sql, (var,))``) so the
+  database driver handles escaping. ORMs do this automatically.
+references:
+  - https://bandit.readthedocs.io/en/latest/plugins/b608_hardcoded_sql_expressions.html
+  - https://cwe.mitre.org/data/definitions/89.html

attocode_intel/rules/packs/community/eslint-typescript/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) <YEAR> <COPYRIGHT HOLDERS>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

attocode_intel/rules/packs/community/eslint-typescript/NOTICE

@@ -0,0 +1,13 @@
+# NOTICE — eslint-typescript
+
+Rule patterns adapted from ESLint core rules (https://github.com/eslint/eslint). Original copyright OpenJS Foundation and contributors. Licensed under MIT.
+
+Upstream: https://github.com/eslint/eslint
+Commit:   (unspecified)
+License:  MIT
+
+Modifications:
+- Translated rule patterns to attocode UnifiedRule schema
+- Subset selection (high-value rules first)
+
+See LICENSE for full license terms.

attocode_intel/rules/packs/community/eslint-typescript/PORTING.md

@@ -0,0 +1,23 @@
+# Porting checklist — eslint-typescript
+
+Rules from eslint (https://github.com/eslint/eslint) are not YAML-defined upstream
+and require manual porting. Each ported rule MUST include the
+attribution comment header at the top of its YAML file:
+
+```yaml
+# Adapted from eslint rule '<original-id>'
+# See ../LICENSE and ../NOTICE for license terms.
+```
+
+Porting targets:
+
+- [ ] no-eval
+- [ ] no-implied-eval
+- [ ] no-new-func
+- [ ] no-script-url
+- [ ] no-return-await
+- [ ] no-var
+- [ ] prefer-const
+- [ ] eqeqeq
+- [ ] no-with
+- [ ] no-throw-literal

attocode_intel/rules/packs/community/eslint-typescript/manifest.yaml

@@ -0,0 +1,14 @@
+name: eslint-typescript
+version: 1.0.0
+languages:
+- typescript
+description: Hand-ported subset of eslint rules. See PORTING.md for the porting checklist.
+source: community
+source_url: https://github.com/eslint/eslint
+source_commit: ''
+source_license: MIT
+attribution: Rule patterns adapted from ESLint core rules (https://github.com/eslint/eslint).
+  Original copyright OpenJS Foundation and contributors. Licensed under MIT.
+imported_at: '2026-04-16T12:20:09Z'
+upstream_rule_count: 10
+imported_rule_count: 0

attocode_intel/rules/packs/community/eslint-typescript/rules/eqeqeq.yaml

@@ -0,0 +1,20 @@
+# Adapted from eslint rule 'eqeqeq'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: eqeqeq
+name: Loose equality comparison
+message: Use === / !== instead of == / !=
+severity: medium
+category: correctness
+languages: [javascript, typescript]
+confidence: 0.85
+pattern: '[^!=<>]==[^=]|[^!]!=[^=]'
+explanation: |
+  ``==`` and ``!=`` perform implicit type coercion, leading to
+  surprising comparisons (``"" == 0`` is true, ``[] == false`` is true).
+  Strict equality avoids the trap.
+recommendation: |
+  Use ``===`` and ``!==``. If type coercion is genuinely intended,
+  add a comment so the next reader knows it's deliberate.
+references:
+  - https://eslint.org/docs/latest/rules/eqeqeq

attocode_intel/rules/packs/community/eslint-typescript/rules/no-eval.yaml

@@ -0,0 +1,22 @@
+# Adapted from eslint rule 'no-eval'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-eval
+name: Dynamic code evaluation
+message: Avoid dynamic code evaluation — arbitrary code execution risk
+severity: critical
+category: security
+languages: [javascript, typescript]
+confidence: 0.85
+cwe: CWE-95
+pattern: '\beval\s*\('
+explanation: |
+  The eval function interprets arbitrary strings as JavaScript and runs
+  them in the local scope. Hard to sandbox; trivial to abuse if any
+  input crosses a trust boundary.
+recommendation: |
+  Use JSON.parse for JSON, a real parser for DSLs, or feature flags /
+  dispatch tables for dynamic behavior.
+references:
+  - https://eslint.org/docs/latest/rules/no-eval
+  - https://cwe.mitre.org/data/definitions/95.html

attocode_intel/rules/packs/community/eslint-typescript/rules/no-implied-eval.yaml

@@ -0,0 +1,20 @@
+# Adapted from eslint rule 'no-implied-eval'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-implied-eval
+name: Implied dynamic code evaluation
+message: setTimeout/setInterval with a string argument runs as code
+severity: high
+category: security
+languages: [javascript, typescript]
+confidence: 0.8
+cwe: CWE-95
+pattern: '\b(setTimeout|setInterval)\s*\(\s*[''"]'
+explanation: |
+  Passing a string (instead of a function) to setTimeout / setInterval
+  evaluates that string as code at the global scope — equivalent to
+  using the eval function.
+recommendation: |
+  Pass an arrow function or function reference: setTimeout(() => doX(), 100).
+references:
+  - https://eslint.org/docs/latest/rules/no-implied-eval

attocode_intel/rules/packs/community/eslint-typescript/rules/no-new-func.yaml

@@ -0,0 +1,21 @@
+# Adapted from eslint rule 'no-new-func'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-new-func
+name: Function constructor used to evaluate code
+message: Function constructor compiles strings into code
+severity: high
+category: security
+languages: [javascript, typescript]
+confidence: 0.85
+cwe: CWE-95
+pattern: '\bnew\s+Function\s*\('
+explanation: |
+  Constructing a function from a string source compiles arbitrary code
+  at runtime, bypassing lexical scope and lint/type analysis.
+recommendation: |
+  Define functions inline or via factory closures. If runtime code
+  generation is genuinely needed, isolate it in a worker with limited
+  capabilities.
+references:
+  - https://eslint.org/docs/latest/rules/no-new-func

attocode_intel/rules/packs/community/eslint-typescript/rules/no-throw-literal.yaml

@@ -0,0 +1,19 @@
+# Adapted from eslint rule 'no-throw-literal'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-throw-literal
+name: Throwing a non-Error literal
+message: Throw an Error subclass, not a raw string or object literal
+severity: medium
+category: correctness
+languages: [javascript, typescript]
+confidence: 0.8
+pattern: '\bthrow\s+[''"`{]'
+explanation: |
+  Throwing a string or object literal loses the stack trace and the
+  ``instanceof Error`` check that downstream catch handlers rely on.
+recommendation: |
+  ``throw new Error("...")`` (or a custom subclass) so callers get the
+  expected interface.
+references:
+  - https://eslint.org/docs/latest/rules/no-throw-literal

attocode_intel/rules/packs/community/eslint-typescript/rules/no-var.yaml

@@ -0,0 +1,20 @@
+# Adapted from eslint rule 'no-var'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-var
+name: Use of var keyword
+message: Prefer let or const over var
+severity: low
+category: style
+languages: [javascript, typescript]
+confidence: 0.95
+pattern: '^\s*var\s+\w'
+explanation: |
+  ``var`` declarations are function-scoped and hoisted, leading to
+  surprising behavior. ``let`` and ``const`` are block-scoped and
+  match developer intuition.
+recommendation: |
+  Replace ``var`` with ``const`` for constants or ``let`` for
+  reassignable bindings.
+references:
+  - https://eslint.org/docs/latest/rules/no-var

attocode_intel/rules/packs/community/eslint-typescript/rules/no-with.yaml

@@ -0,0 +1,18 @@
+# Adapted from eslint rule 'no-with'
+# See ../LICENSE and ../NOTICE for license terms.
+
+id: no-with
+name: Use of with statement
+message: with statement is forbidden in strict mode
+severity: high
+category: correctness
+languages: [javascript, typescript]
+confidence: 0.9
+pattern: '\bwith\s*\('
+explanation: |
+  ``with`` extends the scope chain at runtime, making variable
+  resolution ambiguous. It's banned in strict mode and ES modules.
+recommendation: |
+  Bind the object to a local variable and access fields explicitly.
+references:
+  - https://eslint.org/docs/latest/rules/no-with