memory-journal-mcp 3.0.0

package/.github/workflows/lint-and-test.yml

@@ -0,0 +1,58 @@
+name: Lint and Test
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [ 20.x, 22.x, 25.x ]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v6
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run ESLint
+        run: npm run lint
+
+      - name: Run TypeScript check
+        run: npm run typecheck
+
+      - name: Build
+        run: npm run build
+
+  security-scan:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: '22.x'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run npm audit
+        run: npm audit --audit-level=moderate
+        continue-on-error: true

package/.github/workflows/publish-npm.yml

@@ -0,0 +1,75 @@
+name: Publish to NPM
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version to publish (must match VERSION file or package.json)"
+        required: false
+        default: ""
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment:
+      name: npm
+      url: https://www.npmjs.com/package/memory-journal-mcp
+    
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: '22.x'
+          registry-url: 'https://registry.npmjs.org'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Read version
+        id: version
+        run: |
+          if [ -f "VERSION" ]; then
+            VERSION=$(head -1 VERSION | tr -d '[:space:]')
+          fi
+          if [ -z "$VERSION" ]; then
+            VERSION=$(node -p "require('./package.json').version")
+          fi
+          echo "version=$VERSION" >> $GITHUB_OUTPUT
+          echo "Detected version: $VERSION"
+
+      - name: Verify version matches release tag
+        if: github.event_name == 'release'
+        run: |
+          RELEASE_VERSION="${GITHUB_REF#refs/tags/}"
+          RELEASE_VERSION="${RELEASE_VERSION#v}"
+          PKG_VERSION="${{ steps.version.outputs.version }}"
+          echo "Package version: $PKG_VERSION"
+          echo "Release version: $RELEASE_VERSION"
+          if [ "$PKG_VERSION" != "$RELEASE_VERSION" ]; then
+            echo "Error: Version mismatch!"
+            echo "Expected: $PKG_VERSION"
+            echo "Got: $RELEASE_VERSION"
+            exit 1
+          fi
+
+      - name: Build package
+        run: npm run build
+
+      - name: Publish to NPM
+        run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Verify publication
+        run: |
+          sleep 10
+          npm view memory-journal-mcp version

package/.github/workflows/secrets-scanning.yml

@@ -0,0 +1,32 @@
+name: Secret Scanning
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+permissions:
+  contents: read
+
+jobs:
+  secrets:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: TruffleHog Secret Scanning
+        uses: trufflesecurity/trufflehog@main
+        with:
+          path: ./
+          base: ${{ github.event.before || 'HEAD~1' }}
+          head: HEAD
+          extra_args: --only-verified
+        continue-on-error: true
+
+      - name: GITLEAKS Secret Scanning
+        uses: gitleaks/gitleaks-action@v2
+        continue-on-error: true

package/.github/workflows/security-update.yml

@@ -0,0 +1,99 @@
+name: Security Update Check
+
+on:
+  schedule:
+    # Run weekly on Sundays at 2 AM UTC
+    - cron: '0 2 * * 0'
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+  security-events: write
+  issues: write
+
+jobs:
+  security-scan:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v5
+
+    - name: Set up Docker Buildx
+      uses: docker/setup-buildx-action@v3
+
+    - name: Build image for scanning
+      uses: docker/build-push-action@v6
+      with:
+        context: .
+        file: Dockerfile
+        tags: security-test:latest
+        load: true
+        cache-from: type=gha
+        cache-to: type=gha,mode=max
+
+    # Run SARIF scan first (non-blocking) to always generate the file
+    - name: Run Trivy scanner for SARIF output
+      uses: aquasecurity/trivy-action@master
+      with:
+        image-ref: security-test:latest
+        format: 'sarif'
+        output: 'trivy-results.sarif'
+        exit-code: '0'
+        ignore-unfixed: true
+        severity: 'CRITICAL,HIGH,MEDIUM'
+        trivyignores: '.trivyignore'
+        skip-dirs: '/usr/local/lib/node_modules/npm'
+
+    - name: Upload Trivy scan results
+      uses: github/codeql-action/upload-sarif@v4
+      if: always()
+      with:
+        sarif_file: 'trivy-results.sarif'
+
+    # Run table scan (blocking) after SARIF is uploaded
+    - name: Run Trivy vulnerability scanner
+      uses: aquasecurity/trivy-action@master
+      with:
+        image-ref: security-test:latest
+        format: 'table'
+        exit-code: '1'
+        ignore-unfixed: true
+        severity: 'CRITICAL,HIGH,MEDIUM'
+        trivyignores: '.trivyignore'
+        skip-dirs: '/usr/local/lib/node_modules/npm'
+
+    - name: Create security issue if vulnerabilities found
+      if: failure()
+      uses: actions/github-script@v8
+      with:
+        script: |
+          github.rest.issues.create({
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+            title: '🚨 Security vulnerabilities detected in Docker images',
+            body: `
+            ## Security Alert
+            
+            Trivy has detected security vulnerabilities in our Docker images.
+            
+            **Action Required:**
+            1. Review the security scan results in the Actions tab
+            2. Update base images and dependencies
+            3. Test the fixes
+            4. Deploy updated images
+            
+            **Scan Details:**
+            - Workflow run: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+            - Triggered by: Weekly security scan
+            - Scan Date: ${{ github.event.schedule || 'Manual trigger' }}
+            
+            **Next Steps:**
+            - [ ] Review vulnerability details
+            - [ ] Update Dockerfiles
+            - [ ] Test changes
+            - [ ] Deploy fixes
+            `,
+            labels: ['security', 'vulnerability', 'docker']
+          })

package/.trivyignore

@@ -0,0 +1,18 @@
+# Trivy Ignore File
+# See: https://aquasecurity.github.io/trivy/latest/docs/configuration/filtering/
+
+# CVE-2025-64756: glob command injection in npm CLI (HIGH)
+# This is in the Node.js base image's npm installation (/usr/local/lib/node_modules/npm)
+# We don't use glob CLI directly and cannot patch base image npm
+# Will be fixed when Node.js releases updated base images
+CVE-2025-64756
+
+# CVE-2025-5889: brace-expansion ReDoS (LOW)
+# Bundled in protobufjs/cli/node_modules - can't override with npm
+# LOW severity, attack complexity is high, exploitation is difficult
+CVE-2025-5889
+
+# CVE-2025-54798: tmp symlink vulnerability (LOW)
+# Bundled in protobufjs/cli/node_modules - can't override with npm
+# LOW severity, only affects tmp file creation in CLI context
+CVE-2025-54798

package/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+The D1 Database Manager changelog is maintained in the project wiki.
+
+## 📚 View the Changelog
+
+**Wiki (recommended):** [Changelog](https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG)
+
+**GitHub Repository:** [neverinfamous/memory-journal-mcp](https://github.com/neverinfamous/memory-journal-mcp)
+
+---
+
+The wiki changelog includes:
+- All version history and release notes
+- Detailed feature descriptions
+- Bug fixes and improvements
+- Breaking changes and migration guides
+
+For the latest updates, please refer to the wiki.

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, caste, color, 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
+[INSERT CONTACT METHOD].
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,209 @@
+# Contributing to Memory Journal MCP Server
+
+Thank you for your interest in contributing to the Memory Journal MCP Server! This project is built by developers, for developers, and we welcome contributions that make the journaling experience better for everyone.
+
+## 🚀 Quick Start
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally
+3. **Create a feature branch** from `main`
+4. **Make your changes** and test thoroughly
+5. **Submit a pull request** with a clear description
+
+## 🛠️ Development Setup
+
+### Option 1: Docker Development (Recommended)
+```bash
+# Clone your fork
+git clone https://github.com/YOUR_USERNAME/memory-journal-mcp.git
+cd memory-journal-mcp
+
+# Build and test with Docker
+docker build -f Dockerfile.alpine -t memory-journal-dev .
+docker run --rm -v ./data:/app/data memory-journal-dev python src/server.py
+
+# Test the MCP server
+docker run --rm memory-journal-dev python -c "print('✅ MCP Server ready!')"
+```
+
+### Option 2: Local Development
+```bash
+# Clone your fork
+git clone https://github.com/YOUR_USERNAME/memory-journal-mcp.git
+cd memory-journal-mcp
+
+# Install dependencies
+pip install -r requirements.txt
+
+# Optional: Install semantic search dependencies
+pip install sentence-transformers faiss-cpu
+
+# Test the server
+python src/server.py
+```
+
+## 📋 What We're Looking For
+
+We especially welcome contributions in these areas:
+
+### 🎯 High Priority
+- **New entry types** that make sense for developer workflows
+- **Better Git/GitHub integrations** (more context, better performance)
+- **Performance improvements** (faster search, reduced memory usage)
+- **Bug fixes** and stability improvements
+
+### 🔍 Medium Priority  
+- **Enhanced semantic search** features and models
+- **Import/export utilities** for data portability
+- **Additional relationship types** between entries
+- **Documentation improvements** and examples
+
+### 💡 Future Features
+- **Graph visualization** of entry relationships
+- **Weekly/monthly auto-summaries** 
+- **Team collaboration** features
+- **IDE integrations** beyond MCP
+
+## 🧪 Testing Your Changes
+
+### Manual Testing
+```bash
+# Test basic functionality
+python -c "
+import sys
+sys.path.append('src')
+from server import *
+print('✅ Server imports successfully')
+"
+
+# Test with MCP client (Cursor)
+# Add your local server to ~/.cursor/mcp.json:
+{
+  "mcpServers": {
+    "memory-journal-dev": {
+      "command": "python",
+      "args": ["path/to/your/memory-journal-mcp/src/server.py"]
+    }
+  }
+}
+```
+
+### Docker Testing
+```bash
+# Test alpine build
+docker build -f Dockerfile.alpine -t test-alpine .
+docker run --rm test-alpine python -c "print('Alpine build works!')"
+
+# Test full build  
+docker build -f Dockerfile -t test-full .
+docker run --rm test-full python -c "print('Full build works!')"
+```## 📝 Coding Standards
+
+### Python Code Style
+- **PEP 8 compliance** - Use `black` for formatting
+- **Type hints** - Add type annotations for new functions
+- **Docstrings** - Document public functions and classes
+- **Async/await** - Use async patterns for I/O operations
+- **Error handling** - Implement graceful fallbacks
+
+### Database Changes
+- **Schema migrations** - Update `src/schema.sql` for database changes
+- **Backward compatibility** - Ensure existing data isn't broken
+- **Performance** - Consider index implications for new queries
+- **Testing** - Verify with both empty and populated databases
+
+### Docker Considerations
+- **Multi-stage builds** - Keep images lean
+- **Security** - Run as non-root user, minimal privileges
+- **Compatibility** - Test on both lite and full variants
+- **Documentation** - Update Docker guides if needed
+
+## 🐛 Bug Reports
+
+When reporting bugs, please include:
+
+1. **Environment details** (OS, Python version, Docker version)
+2. **Steps to reproduce** the issue
+3. **Expected vs actual behavior**
+4. **MCP client details** (Cursor version, configuration)
+5. **Relevant logs** or error messages
+6. **Database state** (if applicable)
+
+Use our [Bug Report template](.github/ISSUE_TEMPLATE/bug_report.md) for consistency.
+
+## 💡 Feature Requests
+
+For new features, please provide:
+
+1. **Use case description** - What problem does this solve?
+2. **Proposed solution** - How should it work?
+3. **Developer workflow** - How does this fit into dev work?
+4. **Alternatives considered** - What other approaches did you think about?
+5. **Implementation notes** - Any technical considerations
+
+Use our [Feature Request template](.github/ISSUE_TEMPLATE/feature_request.md).
+
+## 🔄 Pull Request Process
+
+### Before Submitting
+- [ ] **Fork** the repository and create a feature branch
+- [ ] **Test** your changes thoroughly (manual + Docker)
+- [ ] **Update documentation** if you changed APIs or behavior
+- [ ] **Add examples** for new features
+- [ ] **Check** that existing functionality still works
+
+### PR Description Should Include
+- **Summary** of changes made
+- **Testing** performed (how did you verify it works?)
+- **Breaking changes** (if any)
+- **Related issues** (fixes #123)
+- **Screenshots** (for UI changes)
+
+### Review Process
+1. **Automated checks** must pass
+2. **Maintainer review** - we'll provide feedback
+3. **Address feedback** - make requested changes
+4. **Merge** - once approved, we'll merge your PR
+
+## 🎯 Development Tips
+
+### Working with MCP
+- **Test in Cursor** - The primary MCP client environment
+- **Check tool responses** - Ensure JSON responses are well-formed
+- **Handle timeouts** - Git operations should fail fast
+- **Async safety** - All blocking operations in thread pools
+
+### Database Development
+- **Use WAL mode** - Already configured for concurrency
+- **FTS5 integration** - Full-text search is performance-critical
+- **Proper transactions** - Always commit changes
+- **Index optimization** - Consider query performance
+
+### Docker Development
+```bash
+# Quick rebuild and test cycle
+docker build -f Dockerfile.alpine -t dev-test . && \
+docker run --rm -v ./data:/app/data dev-test python src/server.py
+```
+
+## 🤝 Community
+
+- **Be respectful** - Follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+- **Ask questions** - Use GitHub Discussions for help
+- **Share ideas** - Feature requests and feedback welcome
+- **Help others** - Answer questions and review PRs
+
+## 📞 Getting Help
+
+- **GitHub Issues** - Bug reports and feature requests
+- **GitHub Discussions** - Questions and community chat
+- **Documentation** - Check README.md and Docker guides first
+
+## 🏆 Recognition
+
+Contributors are recognized in:
+- **Release notes** - Major contributions highlighted
+- **README** - Contributor acknowledgments
+- **Git history** - Your commits are permanent record
+
+Thank you for helping make Memory Journal MCP Server better for the developer community! 🚀