MCP Trust Score

.gitignore 2

@@ -0,0 +1,32 @@
+# Dependencies
+node_modules/
+venv/
+
+# Build output
+dist/
+build/
+
+# Logs
+logs/
+*.log
+npm-debug.log*
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# IDEs and editors
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# System files
+.DS_Store
+Thumbs.db
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class

.npmrc 2

@@ -0,0 +1 @@
+registry=https://registry.npmjs.org/

CHANGELOG 2.md

@@ -0,0 +1,28 @@
+# 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.0.1] - 2025-04-02
+
+### Fixed
+- Fixed logs directory creation issue where logs were being created in the root directory instead of the application directory
+- Updated both index.ts and mcp-server.ts to use ESM equivalent of __dirname instead of process.cwd()
+
+## [1.0.0] - 2025-03-20
+
+### Added
+- Initial release
+- Natural Language Parser for IDB commands
+- MCP Server implementation
+- IDB Manager with complete command support
+- Orchestrator for command handling
+- Support for all IDB simulator management features
+- Extensive test coverage for core components
+- Command registry with accessibility, app, capture, debug, misc, simulator and UI commands
+- Documentation and examples
+- Security policy
+- Contribution guidelines
+- Code of conduct

CODE_OF_CONDUCT 2.md

@@ -0,0 +1,141 @@
+<!--
+SPDX-FileCopyrightText: 2024 Industria de Diseño Textil S.A. INDITEX
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+# Contributor Covenant Code of Conduct
+
+> Note: This Code of Conduct is a baseline for this project and it doesn't overpass
+current [Inditex's corporate ethics](https://www.inditex.com/itxcomweb/en/group/our-ethical-commitment).
+
+## 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 email 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
+[[email protected]](mailto:[email protected]).
+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

CONTRIBUTING 2.md

@@ -0,0 +1,45 @@
+<!--
+SPDX-FileCopyrightText: 2024 Industria de Diseño Textil S.A. INDITEX
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+# Contributing
+
+Thank you for your interest in contributing to this project! We value and appreciate any contributions you can make.
+To maintain a collaborative and respectful environment, please consider the following guidelines when contributing to
+this project.
+
+## Prerequisites
+
+- Before starting to contribute to the code, you must first sign the [Contributor License Agreement (CLA)](https://github.com/InditexTech/foss/blob/main/documents/ITX_OSS_CLA.pdf).
+
+## How to Contribute
+
+1. Open an issue to discuss and gather feedback on the feature or fix you wish to address.
+2. Fork the repository and clone it to your local machine.
+3. Create a new branch to work on your contribution: `git checkout -b your-branch-name`.
+4. Make the necessary changes in your local branch.
+5. Ensure that your code follows the established project style and formatting guidelines.
+6. Perform testing to ensure your changes do not introduce errors.
+7. Make clear and descriptive commits that explain your changes.
+8. Push your branch to the remote repository: `git push origin your-branch-name`.
+9. Open a pull request describing your changes and linking the corresponding issue.
+10. Await comments and discussions on your pull request. Make any necessary modifications based on the received feedback.
+11. Once your pull request is approved, your contribution will be merged into the main branch.
+
+## Contribution Guidelines
+
+- All contributors are expected to follow the project's [code of conduct](CODE_of_CONDUCT.md). Please be respectful and
+considerate towards other contributors.
+- Before starting work on a new feature or fix, check existing [issues](../../issues) and [pull requests](../../pulls)
+to avoid duplications and unnecessary discussions.
+- If you wish to work on an existing issue, comment on the issue to inform other contributors that you are working on it.
+This will help coordinate efforts and prevent conflicts.
+- It is always advisable to discuss and gather feedback from the community before making significant changes to the
+project's structure or architecture.
+- Ensure a clean and organized commit history. Divide your changes into logical and descriptive commits. We recommend to use the [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/)
+- Document any new changes or features you add. This will help other contributors and project users understand your work
+and its purpose.
+- Be sure to link the corresponding issue in your pull request to maintain proper tracking of contributions.
+- Remember to add license and copyright information following the [REUSE Specification](https://reuse.software/spec/#copyright-and-licensing-information).