VOOZH about

URL: https://deepwiki.com/Digilac/simap-mcp/9.2-code-of-conduct

⇱ Code of Conduct | Digilac/simap-mcp | DeepWiki


Loading...
Menu

Code of Conduct

The simap-mcp project follows the Contributor Covenant 3.0 Code of Conduct. This document defines community standards, behavioral expectations, reporting procedures, and enforcement mechanisms. The code applies to all project spaces: the GitHub repository, issue tracker, pull requests, and official communications.

For security vulnerability reporting, see 9.3 Security Policy For contribution workflows, see 9.1 How to Contribute

Sources: CODE_OF_CONDUCT.md1-90 SECURITY.md1-51


Community Pledge

The project pledges to provide a welcoming, safe, and equitable environment for all participants. Equal participation privileges are extended to everyone acting in good faith and adhering to community standards.

Protected characteristics include:

  • Race, ethnicity, caste, color, age, physical characteristics
  • Neurodiversity, disability, sex, gender identity or expression, sexual orientation
  • Language, philosophy, religion, national or social origin
  • Socio-economic position, level of education, or other status

Sources: CODE_OF_CONDUCT.md3-8


Behavioral Guidelines

Encouraged Behaviors

The code of conduct defines seven core behavioral expectations that promote community well-being:

BehaviorDescription
Purpose RespectRespect the community's purpose, activities, and gathering methods
Kind and Honest EngagementEngage with others kindly and honestly
Viewpoint RespectRespect different viewpoints and experiences
ResponsibilityTake responsibility for actions and contributions
Constructive FeedbackGive and accept constructive feedback gracefully
Harm RepairCommit to repairing harm when it occurs
Community Well-beingPromote and sustain community well-being

Community members acknowledge that social norms vary and that words and actions may be interpreted differently based on culture, background, or language.

Sources: CODE_OF_CONDUCT.md10-23

Restricted Behaviors

The code prohibits seven primary categories of harmful behavior plus four additional restrictions.

Prohibited Behaviors


Sources: CODE_OF_CONDUCT.md25-43


Reporting Process

Reporting Channels

Code of conduct violations should be reported through:

  1. GitHub Issues: https
  2. Email: info@digilac.ch

Security vulnerabilities must not be reported via public issues and should use the private reporting channel defined in SECURITY.md.

Sources: CODE_OF_CONDUCT.md49-50 SECURITY.md13-15

Investigation Flow


Investigation Principles

Community Moderators follow these principles:

PrincipleImplementation
TimelinessRespond to reports promptly CODE_OF_CONDUCT.md51
ThoroughnessInvestigate all reports seriously CODE_OF_CONDUCT.md51
TransparencyKeep actions transparent while prioritizing safety CODE_OF_CONDUCT.md51
ConfidentialityConduct enforcement privately with involved parties CODE_OF_CONDUCT.md51
CommunicationPublic statements only with mutual agreement CODE_OF_CONDUCT.md51

Sources: CODE_OF_CONDUCT.md45-52


Enforcement Framework

Enforcement Ladder

The enforcement ladder provides a graduated response system based on violation severity and community impact. Lower rungs may be skipped for serious violations.


Enforcement Level Details

LevelTrigger EventConsequenceRepair Pathway
1. WarningSingle incident or series of incidents CODE_OF_CONDUCT.md59Private written warning from Community Moderators CODE_OF_CONDUCT.md60Private apology, acknowledgement of responsibility, clarification of expectations CODE_OF_CONDUCT.md61
2. Temporarily Limited ActivitiesRepeated violation after warning, or first serious violation CODE_OF_CONDUCT.md63Private warning with time-limited cooldown period CODE_OF_CONDUCT.md64Apology, reflection during cooldown, thoughtful re-entry CODE_OF_CONDUCT.md65
3. Temporary SuspensionPattern of repeated violations or single serious violation CODE_OF_CONDUCT.md67Private warning with suspension and conditions for return CODE_OF_CONDUCT.md68Respect suspension spirit, meet return conditions, thoughtful reintegration CODE_OF_CONDUCT.md69
4. Permanent BanPattern of violations unresolved by other steps, or extremely serious violation CODE_OF_CONDUCT.md71Removal from all community spaces, tools, and channels CODE_OF_CONDUCT.md72No repair possible CODE_OF_CONDUCT.md73

Sources: CODE_OF_CONDUCT.md54-75


Scope and Applicability

Coverage Areas


The Code of Conduct applies in:

  1. Community Spaces:

  2. Official Representation:

Sources: CODE_OF_CONDUCT.md78-81


Attribution

The code is adapted from Contributor Covenant 3.0:

PropertyValue
StewardOrganization for Ethical Source
LicenseCC BY-SA 4.0
Sourcehttps://www.contributor-covenant.org/version/3/0/
Enforcement InspirationMozilla code of conduct team

Sources: CODE_OF_CONDUCT.md83-89


Implementation in Repository

The code of conduct is implemented in the repository structure as follows:

FileLocationPurpose
CODE_OF_CONDUCT.mdRepository rootFull text of community standards CODE_OF_CONDUCT.md1-90
SECURITY.mdRepository rootVulnerability reporting via private advisories SECURITY.md15
.env.exampleRepository rootGuidance on avoiding sensitive data leaks in debug logs .env.example5-8
Contact emailinfo@digilac.chPrimary reporting channel for violations CODE_OF_CONDUCT.md49
GitHub Issuesgithub.com/Digilac/simap-mcp/issuesPublic reporting channel CODE_OF_CONDUCT.md49

Technical Considerations for Conduct

While the Code of Conduct governs human behavior, the technical implementation of the server includes features to prevent accidental data exposure that could lead to privacy violations (Violating Confidentiality CODE_OF_CONDUCT.md33).

  • Debug Mode Safety: The SIMAP_MCP_DEBUG flag SECURITY.md39-40 should remain unset in production. When enabled via .env env.example8 it switches the HTTP client to verbose stderr logging of full outbound URLs SECURITY.md45-48 Since these logs can contain user-intent data (search terms, CPV codes, canton filters), they are restricted to local troubleshooting to avoid leaking private information into shared infrastructure SECURITY.md50-51
  • Data Confidentiality: The project acts as a read-only client and does not handle authentication or sensitive user data SECURITY.md24 However, improper handling of input validation or tool outputs could lead to unexpected data exposure SECURITY.md28-29

Sources: CODE_OF_CONDUCT.md1-90 SECURITY.md24-51 .env.example1-9