adaptive-memory-multi-model-router 1.9.5 → 2.0.1

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: 🐛 Bug Report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+## 🐛 Bug Description
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1. Install package with `npm install adaptive-memory-multi-model-router`
+2. Run code:
+```javascript
+const { createA3MRouter } = require('adaptive-memory-multi-model-router');
+// Your code here
+```
+3. See error
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+
+What actually happened. Include error messages, stack traces, etc.
+
+## Environment
+
+- **OS**: [e.g., macOS, Linux, Windows]
+- **Node.js version**: [e.g., 18.0.0]
+- **Package version**: [e.g., 1.9.5]
+- **NPM version**: [e.g., 9.0.0]
+
+## Additional Context
+
+Add any other context about the problem here, such as:
+- Provider you're using (Groq, OpenAI, etc.)
+- API keys configured
+- Specific query that caused the issue
+
+## Possible Solution
+
+If you have ideas on how to fix this, please share!

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📖 Documentation
+    url: https://github.com/Das-rebel/adaptive-memory-multi-model-router#readme
+    about: Check the README for usage examples and API documentation
+  - name: 💬 Discussions
+    url: https://github.com/Das-rebel/adaptive-memory-multi-model-router/discussions
+    about: Ask questions and share ideas in our community forum
+  - name: 🚀 NPM Package
+    url: https://www.npmjs.com/package/adaptive-memory-multi-model-router
+    about: View package details and download statistics

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,37 @@
+---
+name: 💡 Feature Request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+
+---
+
+## 💡 Feature Description
+
+A clear and concise description of what you want to happen.
+
+## Problem Statement
+
+Is your feature request related to a problem? Please describe.
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## Proposed Solution
+
+Describe the solution you'd like to see implemented.
+
+## Alternatives Considered
+
+Describe any alternative solutions or features you've considered.
+
+## Use Case
+
+Describe the use case for this feature. Who would benefit and how?
+
+## Additional Context
+
+Add any other context, screenshots, or examples about the feature request here.
+
+## Implementation Ideas
+
+If you have ideas on how this could be implemented, please share!

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+## 📝 Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+
+Fixes # (issue)
+
+## 🔄 Type of Change
+
+Please delete options that are not relevant.
+
+- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
+- [ ] ✨ New feature (non-breaking change which adds functionality)
+- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] 📚 Documentation update
+- [ ] 🎨 Code style/formatting
+- [ ] ⚡ Performance improvement
+- [ ] 🔒 Security improvement
+
+## 🧪 Testing
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+
+- [ ] All existing tests pass (`npm test`)
+- [ ] Added new tests for the changes
+- [ ] Tested manually with example code
+
+## 📋 Checklist
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## 📸 Screenshots (if applicable)
+
+Add screenshots to help explain your changes.
+
+## 💬 Additional Comments
+
+Add any other context or screenshots about the pull request here.

package/.github/workflows/npm-stats-validation.yml

@@ -0,0 +1,152 @@
+name: NPM Stats Validation
+
+on:
+  schedule:
+    # Run daily at 06:00 UTC (after NPM updates at midnight UTC)
+    - cron: '0 6 * * *'
+  workflow_dispatch:  # Allow manual trigger
+  push:
+    branches: [main, master]
+
+jobs:
+  validate-npm-stats:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Fetch NPM Statistics
+        id: npm-stats
+        run: |
+          # Fetch daily stats
+          DAILY=$(curl -s "https://api.npmjs.org/downloads/point/last-day/adaptive-memory-multi-model-router" | jq -r '.downloads // 0')
+          echo "daily=$DAILY" >> $GITHUB_OUTPUT
+          
+          # Fetch weekly stats
+          WEEKLY=$(curl -s "https://api.npmjs.org/downloads/point/last-week/adaptive-memory-multi-model-router" | jq -r '.downloads // 0')
+          echo "weekly=$WEEKLY" >> $GITHUB_OUTPUT
+          
+          # Fetch monthly stats
+          MONTHLY=$(curl -s "https://api.npmjs.org/downloads/point/last-month/adaptive-memory-multi-model-router" | jq -r '.downloads // 0')
+          echo "monthly=$MONTHLY" >> $GITHUB_OUTPUT
+          
+          echo "Daily: $DAILY, Weekly: $WEEKLY, Monthly: $MONTHLY"
+
+      - name: Validate Download Thresholds
+        run: |
+          DAILY=${{ steps.npm-stats.outputs.daily }}
+          WEEKLY=${{ steps.npm-stats.outputs.weekly }}
+          MONTHLY=${{ steps.npm-stats.outputs.monthly }}
+          
+          # Thresholds
+          DAILY_THRESHOLD=100
+          WEEKLY_THRESHOLD=500
+          MONTHLY_THRESHOLD=2000
+          
+          echo "📊 NPM Download Validation"
+          echo "═══════════════════════════════════════════════════════════════"
+          echo ""
+          echo "Current Statistics:"
+          echo "  Daily:   $DAILY downloads (threshold: $DAILY_THRESHOLD)"
+          echo "  Weekly:  $WEEKLY downloads (threshold: $WEEKLY_THRESHOLD)"
+          echo "  Monthly: $MONTHLY downloads (threshold: $MONTHLY_THRESHOLD)"
+          echo ""
+          
+          # Validate
+          FAILED=0
+          
+          if [ "$DAILY" -lt "$DAILY_THRESHOLD" ]; then
+            echo "❌ Daily downloads below threshold: $DAILY < $DAILY_THRESHOLD"
+            FAILED=1
+          else
+            echo "✅ Daily downloads above threshold"
+          fi
+          
+          if [ "$WEEKLY" -lt "$WEEKLY_THRESHOLD" ]; then
+            echo "❌ Weekly downloads below threshold: $WEEKLY < $WEEKLY_THRESHOLD"
+            FAILED=1
+          else
+            echo "✅ Weekly downloads above threshold"
+          fi
+          
+          if [ "$MONTHLY" -lt "$MONTHLY_THRESHOLD" ]; then
+            echo "⚠️ Monthly downloads below threshold: $MONTHLY < $MONTHLY_THRESHOLD (warning only)"
+            # Don't fail for monthly - package is new
+          else
+            echo "✅ Monthly downloads above threshold"
+          fi
+          
+          echo ""
+          
+          if [ "$FAILED" -eq 1 ]; then
+            echo "❌ VALIDATION FAILED"
+            exit 1
+          else
+            echo "✅ VALIDATION PASSED"
+          fi
+
+      - name: Update README Badges
+        if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
+        run: |
+          DAILY=${{ steps.npm-stats.outputs.daily }}
+          WEEKLY=${{ steps.npm-stats.outputs.weekly }}
+          MONTHLY=${{ steps.npm-stats.outputs.monthly }}
+          
+          # Create badge update script
+          cat > update_badges.js << 'EOF'
+          const fs = require('fs');
+          
+          const readme = fs.readFileSync('README.md', 'utf8');
+          
+          // Update download badges
+          let updated = readme;
+          
+          // Daily badge
+          updated = updated.replace(
+            /!\[Daily Downloads\]\([^)]+\)/,
+            `![Daily Downloads](https://img.shields.io/badge/daily-${process.env.DAILY}-blue)`
+          );
+          
+          // Weekly badge  
+          updated = updated.replace(
+            /!\[Weekly Downloads\]\([^)]+\)/,
+            `![Weekly Downloads](https://img.shields.io/badge/weekly-${process.env.WEEKLY}-green)`
+          );
+          
+          // Monthly badge
+          updated = updated.replace(
+            /!\[Monthly Downloads\]\([^)]+\)/,
+            `![Monthly Downloads](https://img.shields.io/badge/monthly-${process.env.MONTHLY}-orange)`
+          );
+          
+          fs.writeFileSync('README.md', updated);
+          console.log('README badges updated');
+          EOF
+          
+          DAILY=$DAILY WEEKLY=$WEEKLY MONTHLY=$MONTHLY node update_badges.js
+
+      - name: Commit Badge Updates
+        if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+          git add README.md
+          git diff --staged --quiet || (git commit -m "📊 Update download badges [daily: ${{ steps.npm-stats.outputs.daily }}, weekly: ${{ steps.npm-stats.outputs.weekly }}]" && git push)
+
+      - name: Post Stats Summary
+        run: |
+          echo "## 📊 NPM Download Statistics" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "| Period | Downloads | Status |" >> $GITHUB_STEP_SUMMARY
+          echo "|--------|-----------|--------|" >> $GITHUB_STEP_SUMMARY
+          echo "| Daily | ${{ steps.npm-stats.outputs.daily }} | ✅ |" >> $GITHUB_STEP_SUMMARY
+          echo "| Weekly | ${{ steps.npm-stats.outputs.weekly }} | ✅ |" >> $GITHUB_STEP_SUMMARY
+          echo "| Monthly | ${{ steps.npm-stats.outputs.monthly }} | ℹ️ |" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "Package: adaptive-memory-multi-model-router" >> $GITHUB_STEP_SUMMARY
+          echo "Validation: PASSED ✅" >> $GITHUB_STEP_SUMMARY

package/.github/workflows/pages.yml

@@ -0,0 +1,37 @@
+name: Deploy GitHub Pages
+
+on:
+  push:
+    branches: [main, master]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: './docs-site'
+
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

package/CHANGELOG.md

@@ -0,0 +1,122 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.9.5] - 2026-05-17
+
+### Added
+- 🔒 **Security Module**: Input validation, prompt injection detection, PII detection
+- 🎯 **GEO Module**: Generative Engine Optimization for AI discoverability
+- 🛡️ Content filtering for hate speech, self-harm, illegal content
+- 📊 Rate limiting with configurable thresholds
+- 🤖 Intent-to-code mapping for AI assistants
+- 📰 6 new articles for LLM discoverability
+- 🎨 SVG logo, banner, and social preview assets
+- 📝 CONTRIBUTING.md, CHANGELOG.md, CODE_OF_CONDUCT.md
+- 🐛 GitHub issue templates and PR template
+- ⚙️ GitHub Action for NPM stats validation
+
+### Changed
+- 📈 Updated README with visual assets and better structure
+- 🔍 Added 17 new keywords for security and GEO
+- 📦 156 total keywords for maximum discoverability
+
+## [1.9.4] - 2026-05-17
+
+### Added
+- 📱 WhatsApp integration export
+- 💬 WhatsApp-Telegram bridge example
+- 🎮 Interactive bridge demo
+
+## [1.9.3] - 2026-05-17
+
+### Added
+- 🧪 Comprehensive test framework (33 tests)
+- 📊 Provider benchmark script
+- 🏥 Provider health check functionality
+
+## [1.9.2] - 2026-05-17
+
+### Added
+- ⚙️ Generic provider configuration system
+- 🔧 User-configurable providers via JSON
+- 📝 Runtime provider registration
+- 🔄 Dynamic model profiles
+
+## [1.9.1] - 2026-05-17
+
+### Added
+- 🎯 Advanced routing with learned algorithm
+- 💰 Cost estimation and tracking
+- 🔄 Automatic fallback chains
+- 📦 12 provider support (API, CLI, Local)
+
+## [1.9.0] - 2026-05-17
+
+### Added
+- ✅ 133 comprehensive tests passing
+- 🎨 139 keywords for discoverability
+- 🔌 116 integrations
+- 📤 76 exports
+- 🖥️ 15 CLI commands
+- 🧠 Memory tree, auto-fetch, obsidian vault
+- 💾 Response caching, prefix caching
+- 🚀 Speculative decoding, batch processing
+
+## [1.8.1] - 2026-05-16
+
+### Fixed
+- 🔍 Memory tree search with punctuation
+- 🔤 Minimum word length for search (2 chars)
+
+## [1.8.0] - 2026-05-16
+
+### Fixed
+- 🐛 14 critical bugs including exports, CLI, cost tracking
+- 📝 CLI rewrite with proper commands
+- 💰 Cost command returning NaN
+
+## [1.7.3] - 2026-05-16
+
+### Added
+- 🔌 Providers subpath export
+
+## [1.7.2] - 2026-05-16
+
+### Added
+- 🧠 Memory API improvements
+
+## [1.7.1] - 2026-05-16
+
+### Added
+- 🏭 createA3MRouter factory function
+- 📤 Proper module exports
+
+## [1.7.0] - 2026-05-16
+
+### Added
+- 🏷️ 139 keywords for AI discoverability
+
+## [1.6.0] - 2026-05-15
+
+### Added
+- 🎉 Initial release
+- 🚀 Core routing functionality
+- 💾 Caching and cost tracking
+- 🔁 Retry and circuit breaker patterns
+
+---
+
+## Release Statistics
+
+| Version | Downloads | Key Feature |
+|---------|-----------|-------------|
+| 1.9.5 | 320/day | Security + GEO |
+| 1.9.0 | 552/day | 133 tests passing |
+| 1.8.0 | Growing | Bug fixes |
+| 1.7.0 | Initial | 139 keywords |
+
+*Total: 872+ weekly downloads*

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[Sdas22@gmail.com](mailto:Sdas22@gmail.com).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -0,0 +1,110 @@
+# Contributing to A3M Router
+
+First off, thank you for considering contributing to A3M Router! It's people like you that make this project a great tool for the community.
+
+## Where to Start?
+
+- 🐛 **Found a bug?** [Open an issue](https://github.com/Das-rebel/adaptive-memory-multi-model-router/issues)
+- 💡 **Have an idea?** [Start a discussion](https://github.com/Das-rebel/adaptive-memory-multi-model-router/discussions)
+- 🔧 **Want to code?** Read on!
+
+## Development Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/Das-rebel/adaptive-memory-multi-model-router.git
+cd adaptive-memory-multi-model-router
+
+# Install dependencies
+npm install
+
+# Run tests
+npm test
+
+# Run linting
+npm run lint
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before creating bug reports, please check the existing issues. When creating a bug report, include:
+
+- **Clear title and description**
+- **Steps to reproduce**
+- **Expected vs actual behavior**
+- **Environment details** (Node version, OS)
+- **Code samples** if applicable
+
+### Suggesting Enhancements
+
+Enhancement suggestions are tracked as GitHub issues. Include:
+
+- **Use case** - Why is this needed?
+- **Proposed solution** - How should it work?
+- **Alternatives** - What else was considered?
+- **Additional context** - Screenshots, examples
+
+### Pull Requests
+
+1. Fork the repo and create your branch from `main`
+2. If you've added code, add tests
+3. If you've changed APIs, update the documentation
+4. Ensure the test suite passes
+5. Make sure your code follows the existing style
+6. Issue that pull request!
+
+### Code Style
+
+- **JavaScript**: Follow existing patterns
+- **TypeScript**: Strict mode enabled
+- **Tests**: All new features need tests
+- **Documentation**: Update README for user-facing changes
+
+## Project Structure
+
+```
+├── dist/           # Compiled JavaScript
+├── src/            # TypeScript source
+├── test/           # Test files
+├── docs/           # Documentation
+├── examples/       # Usage examples
+└── scripts/        # Build and utility scripts
+```
+
+## Areas Needing Help
+
+🎯 **High Priority**
+- Additional LLM provider integrations
+- Performance optimizations
+- Better error handling
+
+🚀 **Nice to Have**
+- More examples
+- Video tutorials
+- Blog posts
+
+📝 **Documentation**
+- Translation to other languages
+- API documentation improvements
+- Usage guides
+
+## Recognition
+
+Contributors will be:
+- Listed in our README
+- Mentioned in release notes
+- Added to the contributors graph
+
+## Questions?
+
+Join our [Discussions](https://github.com/Das-rebel/adaptive-memory-multi-model-router/discussions) or reach out on [Twitter](https://twitter.com/yourhandle).
+
+## Code of Conduct
+
+This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+---
+
+**Thank you for contributing!** 🎉