@mkevenaar/chocolatey-packages
AIf you have any issues with one of the packages hosted in this repository, please feel free to open an issue (preferred instead of using Contact Maintainers on chocolatey.org).
Install
agr install @mkevenaar/chocolatey-packages --target codexWrites 1 file into AGENTS.md, pinned to git-e4f7bd9d.
- AGENTS.md
Document
Agent Instructions
- Never use
curl.exe; use PowerShell or .NET-native tooling instead.
Chocolatey AU Packages
- Fix update logic in
update.ps1or supporting scripts only. - Do not manually edit AU-generated package output such as installer URLs, checksums, checksum types, release notes, or dependency-generated metadata.
- Never manually compute and write package checksums. Checksum updates must be produced by the AU script.
- Never commit any change to a
<version>value in a.nuspecfile. - If an AU run changes a
.nuspecversion during validation, exclude/revert that change before committing and report that AU generated it. - If the local AU run cannot complete because of missing Chocolatey extensions or environment-specific helpers, report the blocker instead of filling generated fields by hand.
- Before finishing AU package work, review
git diffand confirm that no unintended.nuspecversion changes or manual checksum changes are present. - For package-specific commits, prefix the commit subject with the package id in parentheses, followed by a short summary. Example:
(intel-arc-graphics-driver) Fix AU update flow. - For meta-package groups, use the meta package id as the commit prefix when updating all related packages or all related packages except the meta package. For changes limited to one specific package, use that package id instead.
Repository README
Describes mkevenaar/chocolatey-packages as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Chocolatey Packages
Description
If you have any issues with one of the packages hosted in this repository, please feel free to open an issue (preferred instead of using Contact Maintainers on chocolatey.org).
This repository contains Chocolatey packages, most of which are automatically updated.
All packages in this repository should conform with the contributing guidelines. Contributions that follow the guideliness are welcome. All packages in this repository are expected to be installable with any version of Chocolatey being made available in the past 12 months, unless a dependency on Chocolatey has been added.
Etiquette Regarding Communication
When requesting support, try to remember that I am a volunteers that have a live outside of open source and I am not paid to ensure things work for you, so please be considerate of my time when you are asking for things. I have a family that also need time as well and only have so much time to give on a daily basis. A little consideration and patience can go a long way. Thanks for understanding.
The Repository layout
This contains Chocolatey packages, both manually and automatically maintained.
Folder Structure
- automatic - where automatic packages are kept. These are packages that are automatically maintained using Chocolatey-AU.
- deprecated - where deprecated packages are kept. These are packages that are no longer maintained.
- extensions - where extensions packages are kept. These are created by me and are manually pushed.
- icons - Where you keep icon files for the packages. This is done to reduce issues when packages themselves move around.
- manual - where packages that are not automatic are kept.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-e4f7bd9d3b912026-08-06