Gathering detailed insights and metrics for action-docs
Gathering detailed insights and metrics for action-docs
Gathering detailed insights and metrics for action-docs
Gathering detailed insights and metrics for action-docs
npm install action-docs
Typescript
Module System
TypeScript (91.75%)
JavaScript (7.45%)
Dockerfile (0.79%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
96 Stars
381 Commits
28 Forks
3 Watchers
24 Branches
15 Contributors
Updated on Jul 11, 2025
Latest Version
2.5.1
Package Id
action-docs@2.5.1
Unpacked Size
49.42 kB
Size
12.19 kB
File Count
20
Published on
Nov 10, 2024
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
A CLI to generate and update documentation for GitHub actions or workflows, based on the definition .yml
. To update your README in a GitHub workflow you can use the action-docs-action.
1<!-- action-docs-header source="action.yml" --> 2 3<!-- action-docs-description source="action.yml" --> # applicable for actions only 4 5<!-- action-docs-inputs source="action.yml" --> 6 7<!-- action-docs-outputs source="action.yml" --> 8 9<!-- action-docs-runs source="action.yml" --> # applicable for actions only
Optionally you can also add the following section to generate a usage guide, replacing <project> and <version> with the name and version of your project you would like to appear in your usage guide.
1<!-- action-docs-usage source="action.yml" project="<project>" version="<version>" -->
1npm install -g action-docs 2cd <your github action> 3 4# write docs to console 5action-docs 6 7# update README 8action-docs --update-readme
action-docs -u
The following options are available via the CLI
Options:
--version Show version number [boolean]
-t, --toc-level TOC level used for markdown [number] [default: 2]
-a, --action GitHub action file
[deprecated: use "source" instead] [string] [default: "action.yml"]
-s, --source GitHub source file [string] [default: "action.yml"]
--no-banner Print no banner
-u, --update-readme Update readme file. [string]
-l, --line-breaks Used line breaks in the generated docs.
[string] [choices: "CR", "LF", "CRLF"] [default: "LF"]
-n, --include-name-header Include a header with the action/workflow name
[boolean]
--help Show help [boolean]
Action-docs can update your README based on the action.yml
. The following sections can be updated: name header, description, inputs, outputs, usage, and runs. Add the following tags to your README and run action-docs -u
.
1<!-- action-docs-header source="action.yml" --> 2 3<!-- action-docs-description source="action.yml" --> 4 5<!-- action-docs-inputs source="action.yml" --> 6 7<!-- action-docs-outputs source="action.yml" --> 8 9<!-- action-docs-runs action="action.yml" --> 10 11<!-- action-docs-usage action="action.yml" project="<project>" version="<version>" -->
Or to include all of the above, use:
1<!-- action-docs-all source="action.yml" project="<project>" version="<version>" -->
For updating other Markdown files add the name of the file to the command action-docs -u <file>
.
If you need to use another/action.yml
:
source="another/action.yml"
;-s
option like action-docs -s another/action.yml
1action-docs
1action-docs --update-readme
1action-docs --source another/action.yaml
1action-docs --source ./some-dir/action.yml --toc-level 3 --update-readme docs.md
1import { generateActionMarkdownDocs } from 'action-docs' 2 3await generateActionMarkdownDocs({ 4 sourceFile: 'action.yml' 5 tocLevel: 2 6 updateReadme: true 7 readmeFile: 'README.md' 8});
We welcome contributions, please checkout the contribution guide.
This project is released under the MIT License.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 9
Details
Reason
2 existing vulnerabilities detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 1/9 approved changesets -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More