Project on PrintMaster Docs

Targeted Documentation Accuracy Audit

Mon, 01 Jan 0001 00:00:00 +0000

Reviewed PrintMaster source snapshot: 565f4c0 (565f4c0762e467f083f54a9e0e7f6bc23ada56c3), on 2026-10-02. This page summarizes the repository audit record.

This was a targeted, source-based operational accuracy pass, not an exhaustive documentation or security audit, nor a live deployment certification. A follow-up reviewed five server operations and validated their OpenAPI contract; other API operations remain outside scope. Imported source/sourceCommit metadata records provenance, not proof of accuracy. Runtime code at the reviewed snapshot took precedence over stale README, example, and template comments.

Contributing to PrintMaster

Mon, 01 Jan 0001 00:00:00 +0000

Thank you for your interest in contributing to PrintMaster! This document provides guidelines and information to help you get started.

Code of Conduct
Getting Started
Development Setup
Project Structure
Making Changes
Testing
Submitting Changes
Adding Printer Support

Code of Conduct

Please be respectful and constructive in all interactions. We’re building something useful together.

Getting Started

Fork the repository on GitHub
Clone your fork locally
Create a branch for your changes

git clone https://github.com/YOUR_USERNAME/printmaster.git
cd printmaster
git checkout -b feature/your-feature-name

Development Setup

Prerequisites

Go 1.24+ - Download
Git - For version control
PowerShell (Windows) or Bash (Linux/macOS) - For build scripts

Building

# Windows - Build agent
.\build.ps1 agent

# Windows - Build server
.\build.ps1 server

# Windows - Build both
.\build.ps1 both

Running Tests

# Test agent packages
cd agent; go test ./... -v

# Test server packages
cd server; go test ./... -v

Quick Development Workflow

# Windows - Kill existing processes, build, and launch
.\dev\launch.ps1

Project Structure

printmaster/
├── agent/ # Agent binary - printer discovery & monitoring
│ ├── scanner/ # SNMP scanning pipeline
│ │ └── vendor/ # Vendor-specific OID profiles
│ ├── storage/ # SQLite device/metrics storage
│ └── web/ # Embedded web UI
├── server/ # Server binary - multi-agent management
│ ├── handlers/ # HTTP API handlers
│ ├── storage/ # Database layer
│ └── web/ # Embedded web UI
├── common/ # Shared packages (logger, config, etc.)
└── docs/ # Design documentation

Key documentation:

PrintMaster Overview

Mon, 01 Jan 0001 00:00:00 +0000

PrintMaster automatically discovers and monitors network printers and copiers. Built for MSPs, MPS providers, copier dealers, and IT departments managing print fleets.

Why PrintMaster?

PrintMaster was born from real-world frustration managing multi-vendor print fleets. Existing solutions meant juggling multiple tools—PrintAudit for metering, Epson Remote Services for Epson devices, Kyocera Net Manager for Kyocera, Epson Device Admin for local management—each with their own quirks, agents that randomly disconnect, and per-device licensing fees.

Security Policy

Mon, 01 Jan 0001 00:00:00 +0000

Supported Versions

We release security patches for the following versions:

Component	Version	Supported
Agent	latest	:white_check_mark:
Server	latest	:white_check_mark:

We recommend always running the latest version for the best security.

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them privately via one of these methods:

Option 1: GitHub Security Advisories (Preferred)

Go to the Security tab
Click “Report a vulnerability”
Fill out the form with details

Option 2: Email

Send details to the repository owner via GitHub (check profile for contact info).

Project on PrintMaster Docs

Targeted Documentation Accuracy Audit

Contributing to PrintMaster

Table of Contents

Code of Conduct

Getting Started

Development Setup

Prerequisites

Building

Running Tests

Quick Development Workflow

Project Structure

PrintMaster Overview

Why PrintMaster?

Security Policy

Supported Versions

Reporting a Vulnerability

Option 1: GitHub Security Advisories (Preferred)

Option 2: Email