# Installer mark avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de mark pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:mark
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install mark
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#mark
```

  Preuve: nixpkgs package indexes: pkgs/by-name/ma/mark/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Faits du paquet

- **Clé du paquet:** brew:mark
- **Gestionnaire de paquets:** Homebrew
- **Version:** 16.8.10
- **Résumé source:** Sync your markdown files with Confluence pages
- **Page d'accueil:** <https://samizdat.dev>
- **Dépôt:** <https://github.com/kovetskiy/mark>
- **Dernière mise à jour:** 2026-08-02T15:44:23Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- mark (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 16.8.10
## Historique du projet et usages

Mark is a command-line publisher that synchronizes Markdown files from a repository or local workspace into Atlassian Confluence pages.

### Historique du projet

The project was created on GitHub in 2015. Its README frames the tool around a common engineering-docs problem: teams keep Markdown in Git but still need Confluence pages updated for an organization that uses Confluence as the visible documentation system.

Mark developed beyond simple Markdown conversion into a Confluence-specific publisher. The README documents page metadata comments, parent and folder creation, attachments, Confluence macros, GitHub-style alerts, task lists, Mermaid rendering, D2 rendering, PlantUML support, and preservation of inline comments.

### Historique d'adoption

Mark has a visible open-source user base, with the official repository showing more than a thousand stars and hundreds of forks. The supplied package facts show it packaged for Homebrew and Nix, and the README also documents Docker usage for CI or reproducible publishing jobs.

### Modes d'utilisation

Users run mark against one or more Markdown files and provide Confluence connection details by flags, environment variables, or a TOML config file. The CLI can create pages, update existing pages, upload attachments, translate Markdown to Confluence storage HTML, and optionally run in dry-run or compile-only modes.

Credentials are operationally important: the README documents username, password or token, base URL, and config-file options, and explicitly says credentials can be stored in the system-specific configuration file or supplied via CLI/environment variables.

### Pourquoi les passionnés de paquets s'y intéressent

Mark is significant as glueware: it lets teams keep docs reviewable in Git while publishing into a proprietary wiki. For package maintainers, it is a single binary CLI with CI-friendly flags and a clear target audience, rather than another general Markdown renderer.

### Chronologie

- 2015: GitHub repository created.
- 2026: Repository metadata shows ongoing activity and a large issue/PR history.
- 2026: Supplied package facts list Homebrew and Nix packaging.

### Related projects

- Mark sits between Markdown tooling and Atlassian Confluence's REST/storage APIs.
- Its README references optional rendering integrations such as Mermaid, D2, PlantUML, and GitHub-style Markdown alerts.

### Sources

- <https://api.github.com/repos/kovetskiy/mark>
- <https://github.com/kovetskiy/mark>
- <https://github.com/kovetskiy/mark#usage>
- source_facts.package-manager


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour mark. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: $XDG_CONFIG_HOME/mark.toml, ~/.config/mark.toml
- macOS: ~/Library/Application Support/mark.toml
- Windows: %AppData%\mark.toml

## Credential files

- Linux: $XDG_CONFIG_HOME/mark.toml, ~/.config/mark.toml
- macOS: ~/Library/Application Support/mark.toml
- Windows: %AppData%\mark.toml
## Autres enregistrements de gestionnaires de paquets

- Nix - mark: normalized package name match | nixpkgs package indexes: pkgs/by-name/ma/mark/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/mark.yml](https://github.com/mxcl/pkgdb/blob/main/combined/mark.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph