Update readme, remove unused dependencies.

Signed-off-by: Rahul Krishna <i.m.ralk@gmail.com>

Author: rahlk

README.md

@@ -6,15 +6,13 @@ A comprehensive static analysis tool for Python source code that provides symbol
 
 ## Installation
 
-This project uses [uv](https://docs.astral.sh/uv/) for dependency management.
+```bash
+pip install codeanalyzer-python
+```
 
 ### Prerequisites
 
-- [uv](https://docs.astral.sh/uv/getting-started/installation/) installed
-- Python 3.12 or higher. You can use `uv` to install Python if it's not already installed:
-  ```bash
-  uv python install 3.12
-  ```
+- Python 3.12 or higher
 
 #### System Package Requirements
 
@@ -56,36 +54,22 @@ pyenv global 3.12.0   # or pyenv local 3.12.0 for project-specific
 
 > **Note:** These packages are required as the tool uses Python's built-in `venv` module to create isolated environments for analysis.
 
-### Setup
-
-1. Clone the repository:
-   ```bash
-   git clone https://github.com/codellm-devkit/codeanalyzer-python
-   cd codeanalyzer-python
-   ```
-
-2. Install dependencies using uv:
-   ```bash
-   uv sync --all-groups
-   ```
-   This will install all dependencies including development and test dependencies.
-
 ## Usage
 
 The codeanalyzer provides a command-line interface for performing static analysis on Python projects.
 
 ### Basic Usage
 
 ```bash
-uv run codeanalyzer --input /path/to/python/project
+codeanalyzer --input /path/to/python/project
 ```
 
 ### Command Line Options
 
-To view the available options and commands, run `uv run codeanalyzer --help`. You should see output similar to the following:
+To view the available options and commands, run `codeanalyzer --help`. You should see output similar to the following:
 
 ```bash
-❯ uv run codeanalyzer --help
+❯ codeanalyzer --help
 
  Usage: codeanalyzer [OPTIONS] COMMAND [ARGS]...
 
@@ -109,46 +93,46 @@ To view the available options and commands, run `uv run codeanalyzer --help`. Yo
 
 1. **Basic analysis with symbol table:**
    ```bash
-   uv run codeanalyzer --input ./my-python-project
+   codeanalyzer --input ./my-python-project
    ```
 
    This will print the symbol table to stdout in JSON format to the standard output. If you want to save the output, you can use the `--output` option.
 
    ```bash
-   uv run codeanalyzer --input ./my-python-project --output /path/to/analysis-results
+   codeanalyzer --input ./my-python-project --output /path/to/analysis-results
    ```
 
    Now, you can find the analysis results in `analysis.json` in the specified directory.
 
 2. **Toggle analysis levels with `--analysis-level`:**
    ```bash
-   uv run codeanalyzer --input ./my-python-project --analysis-level 1 # Symbol table only
+   codeanalyzer --input ./my-python-project --analysis-level 1 # Symbol table only
    ```
    Call graph analysis can be enabled by setting the level to `2`:
    ```bash
-   uv run codeanalyzer --input ./my-python-project --analysis-level 2 # Symbol table + Call graph
+   codeanalyzer --input ./my-python-project --analysis-level 2 # Symbol table + Call graph
    ```
    ***Note: The `--analysis-level=2` is not yet implemented in this version.***
 
 3. **Analysis with CodeQL enabled:**
    ```bash
-   uv run codeanalyzer --input ./my-python-project --codeql
+   codeanalyzer --input ./my-python-project --codeql
    ```
     This will perform CodeQL-based analysis in addition to the standard symbol table generation. 
 
     ***Note: Not yet fully implemented. Please refrain from using this option until further notice.***
 
 4. **Eager analysis with custom cache directory:**
    ```bash
-   uv run codeanalyzer --input ./my-python-project --eager --cache-dir /path/to/custom-cache
+   codeanalyzer --input ./my-python-project --eager --cache-dir /path/to/custom-cache
    ```
     This will rebuild the analysis cache at every run and store it in `/path/to/custom-cache/.codeanalyzer`. The cache will be cleared by default after analysis unless you specify `--keep-cache`.
 
     If you provide --cache-dir, the cache will be stored in that directory. If not specified, it defaults to `.codeanalyzer` in the current working directory (`$PWD`).
 
 5. **Quiet mode (minimal output):**
    ```bash
-   uv run codeanalyzer --input /path/to/my-python-project --quiet
+   codeanalyzer --input /path/to/my-python-project --quiet
    ```
 
 ### Output
@@ -157,6 +141,32 @@ By default, analysis results are printed to stdout in JSON format. When using th
 
 ## Development
 
+This project uses [uv](https://docs.astral.sh/uv/) for dependency management during development.
+
+### Development Setup
+
+1. Install [uv](https://docs.astral.sh/uv/getting-started/installation/)
+
+2. Clone the repository:
+   ```bash
+   git clone https://github.com/codellm-devkit/codeanalyzer-python
+   cd codeanalyzer-python
+   ```
+
+3. Install dependencies using uv:
+   ```bash
+   uv sync --all-groups
+   ```
+   This will install all dependencies including development and test dependencies.
+
+### Running from Source
+
+When developing, you can run the tool directly from source:
+
+```bash
+uv run codeanalyzer --input /path/to/python/project
+```
+
 ### Running Tests
 
 ```bash

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codeanalyzer-python"
-version = "0.1.3"
+version = "0.1.4"
 description = "Static Analysis on Python source code using Jedi, CodeQL and Treesitter."
 readme = "README.md"
 authors = [
@@ -9,18 +9,15 @@ authors = [
 requires-python = ">=3.12"
 
 dependencies = [
-    "asteroid>=0.7.0",
     "astor>=0.8.1",
     "jedi>=0.19.2",
     "loguru>=0.7.3",
     "networkx>=3.5",
-    "pandas>=2.3.0",
+    "pandas>=2.3.1",
     "pydantic>=2.11.7",
     "requests>=2.32.4",
     "rich>=14.0.0",
-    "ruff>=0.12.2",
-    "toml>=0.10.2",
-    "typer>=0.16.0",
+    "typer>=0.16.0", 
 ]
 
 [dependency-groups]