napt 0.3.1
Automates the entire workflow for packaging Windows applications and deploying them to Microsoft Intune
Requires Python: >=3.11
Keywords: intune, intunewin, msi, psadt, packaging, windows, deployment, automation

# NAPT - Not a Pkg Tool

> **Automated Windows application packaging and deployment to Microsoft Intune using PSAppDeployToolkit**

[![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)

## Overview

NAPT is a Python-based CLI tool that automates the entire workflow for packaging Windows applications and deploying them to Microsoft Intune. It runs on Windows, Linux, and macOS, though packaging (.intunewin creation) requires Windows.

📚 **[Full Documentation](https://rogercibrian.github.io/notapkgtool/)** | [Quick Start](https://rogercibrian.github.io/notapkgtool/quick-start/) | [User Guide](https://rogercibrian.github.io/notapkgtool/user-guide/) | [Developer Reference](https://rogercibrian.github.io/notapkgtool/api/core/)

### Why NAPT?

Packaging applications for Microsoft Intune with PSAppDeployToolkit (PSADT) typically involves a manual, time-consuming process:

1. **Manually check for new versions** - Check vendor sites/APIs for updates. Easy to miss versions or waste time when nothing changed.

2. **Create PSADT deployment** - Copy template, manually edit `Invoke-AppDeployToolkit.ps1` with variables, configure install/uninstall logic. Error-prone and repetitive.

3. **Create detection and requirements scripts** - Write PowerShell detection and requirements logic, test thoroughly, maintain version checks. Must update for each new version.

4. **Package as .intunewin** - Run IntuneWinAppUtil.exe manually, manage paths, handle errors. Tedious and error-prone.

5. **Upload to Intune** - Upload package via portal, fill metadata, configure app info and requirements manually.

6. **Configure deployment** - Set up rollout assignments manually for each version.

This manual workflow is repetitive, difficult to automate in CI/CD pipelines, lacks version tracking, and requires re-doing most of the work for every update. NAPT automates this entire workflow with YAML-based recipes and automatic version tracking.

### Key Features

- ✅ **Automatic version tracking** - Automatic discovery from MSI, EXE, URLs, or APIs with caching to skip unnecessary downloads
- ✅ **YAML-based recipes** - Define app packaging once with layered configuration (Organization → Vendor → Recipe)
- ✅ **Automated PSADT packaging** - Generate Intune-ready packages with detection and requirements scripts, no manual template editing
- ✅ **Cross-platform workflow** - Run on Windows, Linux, and macOS (packaging requires Windows)
- 🚧 **Direct Intune upload** - Automatic deployment (planned)

## Cross-Platform Support

| Feature | Windows | Linux/macOS |
|---------|---------|-------------|
| Discovery & Download | ✅ | ✅ |
| PSADT Package Building | ✅ | ✅ |
| Intune Packaging | ✅ | ⚫ Windows Only |

See the [Cross-Platform Support](https://rogercibrian.github.io/notapkgtool/user-guide/#cross-platform-support) section for platform-specific workflows.

## Getting Started

See the [Quick Start Guide](https://rogercibrian.github.io/notapkgtool/quick-start/) for installation and setup.

## Creating Recipes

Recipes are YAML configuration files that define how to discover, download, and package applications.

**Example recipes:**

- **[chrome.yaml](https://github.com/RogerCibrian/notapkgtool/blob/main/recipes/Google/chrome.yaml)** - url_download strategy with MSI version extraction
- **[git.yaml](https://github.com/RogerCibrian/notapkgtool/blob/main/recipes/Git/git.yaml)** - api_github strategy for GitHub Releases
- **[7zip-x64-msi.yaml](https://github.com/RogerCibrian/notapkgtool/blob/main/recipes/7-Zip/7zip-x64-msi.yaml)** - web_scrape strategy for vendor download pages

NAPT supports multiple discovery strategies (url_download, web_scrape, api_github, api_json) - see the [Discovery Strategies](https://rogercibrian.github.io/notapkgtool/user-guide/#discovery-strategies) guide for detailed configuration and more examples.

## Contributing

Ideas and feedback are welcome! See [Contributing](https://rogercibrian.github.io/notapkgtool/contributing/) for guidelines.

## License

This project is licensed under the Apache License 2.0 - see the [LICENSE](https://github.com/RogerCibrian/notapkgtool/blob/main/LICENSE) file for details.

## Author

**Roger Cibrian**

## Acknowledgments

- Draws inspiration from [AutoPkg](https://github.com/autopkg/autopkg) for macOS application packaging automation
- Uses [PSAppDeployToolkit](https://psappdeploytoolkit.com/) (PSADT) for Windows application packaging
- Uses [IntuneWinAppUtil](https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool) for creating .intunewin packages