paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 43 Packages Projects Releases Wiki Activity

Reworded based on feedback

Browse Source 
Signed-off-by: Andre Wanlin <awanlin@spotify.com>
This commit is contained in:
Andre Wanlin
2026-02-17 17:20:16 -06:00
parent d00a492570
commit eebe94421a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins/plugin-directory-audit.md
+3 -3
View File
@@ -9,9 +9,9 @@ description: Details about the process for auditing plugins in the directory
We have a simple process in place to audit the plugins in the Plugin Directory:
1. On a quarterly basis we run the following script: `node ./scripts/plugin-directory-audit.js --audit`
2. This script will flag any plugin that has not been updated on NPM in more than 365 days as `archived` if it was `inactive`.
3. It will also flag any plugin as `inactive` that has not been updated on NPM in more than 365 days if it was `active`.
4. For any plugin flagged as `inactive` or `archived` and have been updated on NPM in less than 365 days they will be flagged as `active` again.
2. This script will flag any plugin as `inactive` that has not been updated on NPM in more than 365 days if it was `active`.
3. It will also flag any plugin that has not been updated on NPM in more than 365 days as `archived` if it was `inactive`.
4. For any plugin flagged as `inactive` or `archived` and has been updated on NPM in less than 365 days they will be flagged as `active` again.
5. These changes will then be submitted as a PR, approved and merged.
The impact of a plugin being set to `inactive` means they will show in the inactive section at the bottom of the Plugin Directory. A plugin that is set to `archived` will **not** show up in the Plugin Directory at all.