NAPT - Not a Pkg Tool

Automated Windows application packaging and deployment to Microsoft Intune using PSAppDeployToolkit

Overview

NAPT is a Python CLI that automates packaging Windows apps for Microsoft Intune. It runs on Windows, Linux, and macOS; creating .intunewin packages requires Windows.

Full documentation | Quick start | User guide | Developer reference

What NAPT automates

Without NAPT, each new app version means checking the vendor for a release, editing a PSAppDeployToolkit (PSADT) template, writing detection and requirements scripts, running IntuneWinAppUtil.exe, uploading in the Intune portal, and assigning the app to groups. NAPT does each step from one YAML recipe per app.

Key features

• Version discovery - Finds new versions from vendor APIs, GitHub releases, download pages, or fixed URLs, and does not download an unchanged installer again
• YAML recipes - One recipe per app, with layered configuration (organization, vendor, parent recipe, recipe)
• PSADT packaging - Builds the PSADT deployment with detection and requirements scripts, then the .intunewin package
• Intune upload - Uploads to Microsoft Intune through the Graph API
• Ring promotion - napt promote moves each release through deployment rings and reports assignment drift; napt status shows every app's published version, pending release, and ring positions
• Tenant setup and sign-in - napt auth setup creates the Entra app registration with the permissions NAPT needs; napt auth login signs in

Getting started

See the Quick start guide for installation and setup.

Creating recipes

Recipes are YAML files that define how to discover, download, and package an application.

Example recipes:

• chrome.yaml - url_download strategy with MSI version extraction
• git.yaml - api_github strategy for GitHub Releases
• 7zip-x64-msi.yaml - web_scrape strategy for vendor download pages

Note: The recipes/ and defaults/ directories in this repository are working examples used for development and testing. They are not included in the pip package. Run napt init to create your own workspace with a starter org.yaml.

A recipe uses one of four discovery strategies: url_download, web_scrape, api_github, or api_json. The Recipe reference defines their fields; Common tasks walks through a recipe for each.

Contributing

See Contributing to suggest features or report problems.

License

Apache License 2.0; see LICENSE.

Author

Roger Cibrian

Acknowledgments

• Draws inspiration from AutoPkg for macOS application packaging automation
• Uses PSAppDeployToolkit (PSADT) for Windows application packaging
• Uses IntuneWinAppUtil for creating .intunewin packages