trust-path 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- trust_path-0.1.0/.github/workflows/release.yml +52 -0
- trust_path-0.1.0/.github/workflows/test.yml +42 -0
- trust_path-0.1.0/LICENSE +202 -0
- trust_path-0.1.0/MANIFEST.in +5 -0
- trust_path-0.1.0/PKG-INFO +129 -0
- trust_path-0.1.0/README.md +108 -0
- trust_path-0.1.0/pyproject.toml +35 -0
- trust_path-0.1.0/setup.cfg +4 -0
- trust_path-0.1.0/tests/__init__.py +0 -0
- trust_path-0.1.0/tests/fixtures/agent/.github/workflows/triage.yml +16 -0
- trust_path-0.1.0/tests/fixtures/anchors/.github/workflows/a.yml +7 -0
- trust_path-0.1.0/tests/fixtures/head_checkout/.github/workflows/build.yml +17 -0
- trust_path-0.1.0/tests/fixtures/missing_call/.github/workflows/call.yml +4 -0
- trust_path-0.1.0/tests/fixtures/pr_title/.github/workflows/greet.yml +12 -0
- trust_path-0.1.0/tests/fixtures/reusable/.github/workflows/on-comment.yml +12 -0
- trust_path-0.1.0/tests/fixtures/reusable/.github/workflows/reply.yml +21 -0
- trust_path-0.1.0/tests/fixtures/safe/.github/workflows/echo-title.yml +10 -0
- trust_path-0.1.0/tests/fixtures/safe/.github/workflows/label.yml +11 -0
- trust_path-0.1.0/tests/fixtures/safe/.github/workflows/release.yml +15 -0
- trust_path-0.1.0/tests/fixtures/safe/.github/workflows/test.yml +14 -0
- trust_path-0.1.0/tests/fixtures/workflow_run_chain/.github/workflows/ci.yml +8 -0
- trust_path-0.1.0/tests/fixtures/workflow_run_chain/.github/workflows/publish.yml +16 -0
- trust_path-0.1.0/tests/fixtures/workflow_run_chain/.github/workflows/stage.yml +11 -0
- trust_path-0.1.0/tests/test_analyze.py +413 -0
- trust_path-0.1.0/tests/test_cli.py +262 -0
- trust_path-0.1.0/tests/test_yamlsubset.py +202 -0
- trust_path-0.1.0/trust_path/__init__.py +3 -0
- trust_path-0.1.0/trust_path/__main__.py +5 -0
- trust_path-0.1.0/trust_path/analyze.py +444 -0
- trust_path-0.1.0/trust_path/cli.py +58 -0
- trust_path-0.1.0/trust_path/yamlsubset.py +491 -0
- trust_path-0.1.0/trust_path.egg-info/PKG-INFO +129 -0
- trust_path-0.1.0/trust_path.egg-info/SOURCES.txt +34 -0
- trust_path-0.1.0/trust_path.egg-info/dependency_links.txt +1 -0
- trust_path-0.1.0/trust_path.egg-info/entry_points.txt +2 -0
- trust_path-0.1.0/trust_path.egg-info/top_level.txt +1 -0
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# SPDX-License-Identifier: Apache-2.0
|
|
2
|
+
# Publishes a version tag to PyPI through trusted publishing: no token is stored anywhere.
|
|
3
|
+
# The publish job runs in the "pypi" environment, which waits for the owner's approval.
|
|
4
|
+
name: release
|
|
5
|
+
|
|
6
|
+
on:
|
|
7
|
+
push:
|
|
8
|
+
tags: ["v*"]
|
|
9
|
+
|
|
10
|
+
permissions:
|
|
11
|
+
contents: read
|
|
12
|
+
|
|
13
|
+
jobs:
|
|
14
|
+
build:
|
|
15
|
+
runs-on: ubuntu-22.04
|
|
16
|
+
steps:
|
|
17
|
+
- uses: actions/checkout@v4
|
|
18
|
+
- uses: actions/setup-python@v5
|
|
19
|
+
with:
|
|
20
|
+
python-version: "3.13"
|
|
21
|
+
# A tag that disagrees with the package version must never publish.
|
|
22
|
+
- name: Tag matches the package version
|
|
23
|
+
run: |
|
|
24
|
+
version=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
|
|
25
|
+
test "v$version" = "$GITHUB_REF_NAME"
|
|
26
|
+
- run: python -m pip install build twine
|
|
27
|
+
- run: python -m build
|
|
28
|
+
- run: python -m twine check --strict dist/*
|
|
29
|
+
# The sdist must carry everything its own test suite needs.
|
|
30
|
+
- name: Tests pass from the unpacked sdist
|
|
31
|
+
run: |
|
|
32
|
+
mkdir sdist-check
|
|
33
|
+
tar -xzf dist/*.tar.gz -C sdist-check
|
|
34
|
+
cd sdist-check/*/
|
|
35
|
+
python -m unittest discover -s tests
|
|
36
|
+
- uses: actions/upload-artifact@v4
|
|
37
|
+
with:
|
|
38
|
+
name: dist
|
|
39
|
+
path: dist/
|
|
40
|
+
|
|
41
|
+
publish:
|
|
42
|
+
needs: build
|
|
43
|
+
runs-on: ubuntu-22.04
|
|
44
|
+
environment: pypi
|
|
45
|
+
permissions:
|
|
46
|
+
id-token: write # proves this workflow's identity to PyPI; nothing else
|
|
47
|
+
steps:
|
|
48
|
+
- uses: actions/download-artifact@v4
|
|
49
|
+
with:
|
|
50
|
+
name: dist
|
|
51
|
+
path: dist/
|
|
52
|
+
- uses: pypa/gh-action-pypi-publish@release/v1
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
name: test
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
pull_request:
|
|
6
|
+
|
|
7
|
+
permissions:
|
|
8
|
+
contents: read
|
|
9
|
+
|
|
10
|
+
jobs:
|
|
11
|
+
test:
|
|
12
|
+
strategy:
|
|
13
|
+
fail-fast: false
|
|
14
|
+
matrix:
|
|
15
|
+
os: [ubuntu-22.04, macos-15, windows-2022]
|
|
16
|
+
python: ["3.9", "3.13"]
|
|
17
|
+
runs-on: ${{ matrix.os }}
|
|
18
|
+
steps:
|
|
19
|
+
- uses: actions/checkout@v4
|
|
20
|
+
with:
|
|
21
|
+
persist-credentials: false
|
|
22
|
+
- uses: actions/setup-python@v5
|
|
23
|
+
with:
|
|
24
|
+
python-version: ${{ matrix.python }}
|
|
25
|
+
- run: python -m unittest discover -s tests -v
|
|
26
|
+
- run: |
|
|
27
|
+
python -m pip install .
|
|
28
|
+
trust-path .
|
|
29
|
+
|
|
30
|
+
# The package PyPI would receive: built and checked on every change.
|
|
31
|
+
package:
|
|
32
|
+
runs-on: ubuntu-22.04
|
|
33
|
+
steps:
|
|
34
|
+
- uses: actions/checkout@v4
|
|
35
|
+
with:
|
|
36
|
+
persist-credentials: false
|
|
37
|
+
- uses: actions/setup-python@v5
|
|
38
|
+
with:
|
|
39
|
+
python-version: "3.13"
|
|
40
|
+
- run: python -m pip install build twine
|
|
41
|
+
- run: python -m build
|
|
42
|
+
- run: python -m twine check --strict dist/*
|
trust_path-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,129 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: trust-path
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: List the paths by which untrusted input can reach secrets and publishing credentials in GitHub Actions workflows.
|
|
5
|
+
License-Expression: Apache-2.0
|
|
6
|
+
Project-URL: Homepage, https://github.com/jacob-adm/trust-path
|
|
7
|
+
Project-URL: Documentation, https://github.com/jacob-adm/trust-path/tree/main/docs
|
|
8
|
+
Project-URL: Source, https://github.com/jacob-adm/trust-path
|
|
9
|
+
Project-URL: Issues, https://github.com/jacob-adm/trust-path/issues
|
|
10
|
+
Keywords: github-actions,security,secrets,ci,supply-chain,cli
|
|
11
|
+
Classifier: Environment :: Console
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: Operating System :: OS Independent
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
16
|
+
Classifier: Topic :: Security
|
|
17
|
+
Requires-Python: >=3.9
|
|
18
|
+
Description-Content-Type: text/markdown
|
|
19
|
+
License-File: LICENSE
|
|
20
|
+
Dynamic: license-file
|
|
21
|
+
|
|
22
|
+
# trust-path
|
|
23
|
+
|
|
24
|
+
trust-path lists the paths by which untrusted input can reach a secret or a publishing credential
|
|
25
|
+
in a repository's GitHub Actions workflows. Untrusted input is text or code that anyone can supply:
|
|
26
|
+
a pull request title, an issue body, a comment, a fork's branch name or code. A sink is what that
|
|
27
|
+
input can reach: a secret, an OIDC token (`id-token: write`), a write permission of the workflow
|
|
28
|
+
token, a deployment environment, or an AI agent action holding a credential.
|
|
29
|
+
|
|
30
|
+
Attacks in 2026 used these paths. A crafted pull request title made AI agent actions leak their
|
|
31
|
+
secrets, text in issues steered agents, and a worm read OIDC publish tokens from runner memory and
|
|
32
|
+
published packages with them. trust-path shows where such paths exist, including paths that cross
|
|
33
|
+
from one workflow to another through `workflow_run` and reusable workflows. It reports; it does not
|
|
34
|
+
change workflows or decide what to do about a path.
|
|
35
|
+
|
|
36
|
+
[zizmor](https://github.com/zizmorcore/zizmor) and [poutine](https://github.com/boostsecurityio/poutine)
|
|
37
|
+
check many more things. They report an untrusted input, a broad secret or a broad permission at the
|
|
38
|
+
place in a file where it appears. trust-path adds three things: it pairs each source with the
|
|
39
|
+
secret, permission or environment it reaches; it follows a source from one workflow to the next
|
|
40
|
+
through `workflow_run` chains and local reusable workflows; and it treats AI agent actions as
|
|
41
|
+
sinks. See [Using it with other tools](https://github.com/jacob-adm/trust-path/blob/main/docs/other-tools.md).
|
|
42
|
+
|
|
43
|
+
## Requirements
|
|
44
|
+
|
|
45
|
+
- Python 3.9 or later, standard library only.
|
|
46
|
+
- Written for Linux, macOS and Windows. The tests have been run on macOS with Python 3.9 and
|
|
47
|
+
3.14; `.github/workflows/test.yml` runs them on all three systems with Python 3.9 and 3.13
|
|
48
|
+
where GitHub Actions is enabled.
|
|
49
|
+
|
|
50
|
+
## Install
|
|
51
|
+
|
|
52
|
+
From a clone:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
git clone https://github.com/jacob-adm/trust-path
|
|
56
|
+
cd trust-path
|
|
57
|
+
pip install .
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
pip installs `trust-path` as a console script. Without installing, it runs from a clone as
|
|
61
|
+
`python3 -m trust_path`.
|
|
62
|
+
|
|
63
|
+
## How it works
|
|
64
|
+
|
|
65
|
+
1. **Read the workflows.** trust-path reads every `.yml` and `.yaml` file in
|
|
66
|
+
`DIR/.github/workflows` with its own YAML reader, which refuses any construct it does not read
|
|
67
|
+
rather than guess. A refused file is named on standard error with the reason, the other files
|
|
68
|
+
are still checked, and the exit status is 2.
|
|
69
|
+
2. **Find untrusted runs.** A workflow runs with untrusted input when it has a trigger such as
|
|
70
|
+
`pull_request_target`, `issues` or `issue_comment`, when it runs on `workflow_run` after such a
|
|
71
|
+
workflow or after a `pull_request` workflow (followed through chains), or when it is a local
|
|
72
|
+
reusable workflow called from such a run.
|
|
73
|
+
3. **Find where input enters each job.** A step enters untrusted input when it uses a context such
|
|
74
|
+
as `github.event.pull_request.title` in `run:`, `with:` or `env:`, checks out or fetches the pull
|
|
75
|
+
request's head, downloads an artifact from the upstream run, or is an AI agent action.
|
|
76
|
+
4. **Collect what it reaches.** The entry step and every later step of the same job are reached.
|
|
77
|
+
trust-path collects the secrets they use and the job's write permissions, `id-token: write`,
|
|
78
|
+
environment and AI agent actions holding a credential.
|
|
79
|
+
5. **Print one record per path.** Each record is `source`, `workflow`, `job`, `step` and `sink`,
|
|
80
|
+
tab-separated and sorted. Like `grep`, trust-path exits 1 when it finds a path, 0 when it finds
|
|
81
|
+
none and 2 on an error, including any refused file.
|
|
82
|
+
|
|
83
|
+
## Commands
|
|
84
|
+
|
|
85
|
+
```
|
|
86
|
+
trust-path [--json] DIR
|
|
87
|
+
trust-path [--json] --ref REF [DIR]
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
`--json` writes the records as a JSON array. `--ref REF` reads the workflows from git at a branch,
|
|
91
|
+
tag or commit without checking it out; it is the only option that runs git. See [Command](https://github.com/jacob-adm/trust-path/blob/main/docs/commands.md) for the fields and
|
|
92
|
+
exit status.
|
|
93
|
+
|
|
94
|
+
## Quick start
|
|
95
|
+
|
|
96
|
+
From a clone, run it on the test fixture with an AI agent action:
|
|
97
|
+
|
|
98
|
+
```sh
|
|
99
|
+
trust-path tests/fixtures/agent
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
```text
|
|
103
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 agent:anthropics/claude-code-action
|
|
104
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 permissions.issues:write
|
|
105
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 secrets.ANTHROPIC_API_KEY
|
|
106
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 agent:anthropics/claude-code-action
|
|
107
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 permissions.issues:write
|
|
108
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 secrets.ANTHROPIC_API_KEY
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
The workflow runs when an issue is opened and gives `anthropics/claude-code-action` the issue body
|
|
112
|
+
in its prompt, an API key and a token that can write issues. Anyone who can open an issue writes
|
|
113
|
+
that text, and the agent acts on it while holding the key and can write text into issues that
|
|
114
|
+
other workflows and agents read. Run `trust-path .` in a repository checkout to check its workflows.
|
|
115
|
+
|
|
116
|
+
## Documentation
|
|
117
|
+
|
|
118
|
+
- [How trust-path finds paths](https://github.com/jacob-adm/trust-path/blob/main/docs/model.md): sources, entry points, sinks, the AI agent action
|
|
119
|
+
list and the YAML subset.
|
|
120
|
+
- [Command](https://github.com/jacob-adm/trust-path/blob/main/docs/commands.md): output fields, JSON, exit status and an example across workflows.
|
|
121
|
+
- [Limitations and security](https://github.com/jacob-adm/trust-path/blob/main/docs/limitations-and-security.md): what trust-path does not see, read or do.
|
|
122
|
+
- [Using it with other tools](https://github.com/jacob-adm/trust-path/blob/main/docs/other-tools.md): a tested stack with git surface
|
|
123
|
+
and git-overlap, and what zizmor and poutine cover and what trust-path adds.
|
|
124
|
+
- [Contributing](https://github.com/jacob-adm/trust-path/blob/main/CONTRIBUTING.md): running the tests and contributing a change.
|
|
125
|
+
- [Reporting a vulnerability](https://github.com/jacob-adm/trust-path/blob/main/SECURITY.md)
|
|
126
|
+
|
|
127
|
+
## License
|
|
128
|
+
|
|
129
|
+
Apache License 2.0; see [LICENSE](https://github.com/jacob-adm/trust-path/blob/main/LICENSE).
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# trust-path
|
|
2
|
+
|
|
3
|
+
trust-path lists the paths by which untrusted input can reach a secret or a publishing credential
|
|
4
|
+
in a repository's GitHub Actions workflows. Untrusted input is text or code that anyone can supply:
|
|
5
|
+
a pull request title, an issue body, a comment, a fork's branch name or code. A sink is what that
|
|
6
|
+
input can reach: a secret, an OIDC token (`id-token: write`), a write permission of the workflow
|
|
7
|
+
token, a deployment environment, or an AI agent action holding a credential.
|
|
8
|
+
|
|
9
|
+
Attacks in 2026 used these paths. A crafted pull request title made AI agent actions leak their
|
|
10
|
+
secrets, text in issues steered agents, and a worm read OIDC publish tokens from runner memory and
|
|
11
|
+
published packages with them. trust-path shows where such paths exist, including paths that cross
|
|
12
|
+
from one workflow to another through `workflow_run` and reusable workflows. It reports; it does not
|
|
13
|
+
change workflows or decide what to do about a path.
|
|
14
|
+
|
|
15
|
+
[zizmor](https://github.com/zizmorcore/zizmor) and [poutine](https://github.com/boostsecurityio/poutine)
|
|
16
|
+
check many more things. They report an untrusted input, a broad secret or a broad permission at the
|
|
17
|
+
place in a file where it appears. trust-path adds three things: it pairs each source with the
|
|
18
|
+
secret, permission or environment it reaches; it follows a source from one workflow to the next
|
|
19
|
+
through `workflow_run` chains and local reusable workflows; and it treats AI agent actions as
|
|
20
|
+
sinks. See [Using it with other tools](https://github.com/jacob-adm/trust-path/blob/main/docs/other-tools.md).
|
|
21
|
+
|
|
22
|
+
## Requirements
|
|
23
|
+
|
|
24
|
+
- Python 3.9 or later, standard library only.
|
|
25
|
+
- Written for Linux, macOS and Windows. The tests have been run on macOS with Python 3.9 and
|
|
26
|
+
3.14; `.github/workflows/test.yml` runs them on all three systems with Python 3.9 and 3.13
|
|
27
|
+
where GitHub Actions is enabled.
|
|
28
|
+
|
|
29
|
+
## Install
|
|
30
|
+
|
|
31
|
+
From a clone:
|
|
32
|
+
|
|
33
|
+
```
|
|
34
|
+
git clone https://github.com/jacob-adm/trust-path
|
|
35
|
+
cd trust-path
|
|
36
|
+
pip install .
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
pip installs `trust-path` as a console script. Without installing, it runs from a clone as
|
|
40
|
+
`python3 -m trust_path`.
|
|
41
|
+
|
|
42
|
+
## How it works
|
|
43
|
+
|
|
44
|
+
1. **Read the workflows.** trust-path reads every `.yml` and `.yaml` file in
|
|
45
|
+
`DIR/.github/workflows` with its own YAML reader, which refuses any construct it does not read
|
|
46
|
+
rather than guess. A refused file is named on standard error with the reason, the other files
|
|
47
|
+
are still checked, and the exit status is 2.
|
|
48
|
+
2. **Find untrusted runs.** A workflow runs with untrusted input when it has a trigger such as
|
|
49
|
+
`pull_request_target`, `issues` or `issue_comment`, when it runs on `workflow_run` after such a
|
|
50
|
+
workflow or after a `pull_request` workflow (followed through chains), or when it is a local
|
|
51
|
+
reusable workflow called from such a run.
|
|
52
|
+
3. **Find where input enters each job.** A step enters untrusted input when it uses a context such
|
|
53
|
+
as `github.event.pull_request.title` in `run:`, `with:` or `env:`, checks out or fetches the pull
|
|
54
|
+
request's head, downloads an artifact from the upstream run, or is an AI agent action.
|
|
55
|
+
4. **Collect what it reaches.** The entry step and every later step of the same job are reached.
|
|
56
|
+
trust-path collects the secrets they use and the job's write permissions, `id-token: write`,
|
|
57
|
+
environment and AI agent actions holding a credential.
|
|
58
|
+
5. **Print one record per path.** Each record is `source`, `workflow`, `job`, `step` and `sink`,
|
|
59
|
+
tab-separated and sorted. Like `grep`, trust-path exits 1 when it finds a path, 0 when it finds
|
|
60
|
+
none and 2 on an error, including any refused file.
|
|
61
|
+
|
|
62
|
+
## Commands
|
|
63
|
+
|
|
64
|
+
```
|
|
65
|
+
trust-path [--json] DIR
|
|
66
|
+
trust-path [--json] --ref REF [DIR]
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
`--json` writes the records as a JSON array. `--ref REF` reads the workflows from git at a branch,
|
|
70
|
+
tag or commit without checking it out; it is the only option that runs git. See [Command](https://github.com/jacob-adm/trust-path/blob/main/docs/commands.md) for the fields and
|
|
71
|
+
exit status.
|
|
72
|
+
|
|
73
|
+
## Quick start
|
|
74
|
+
|
|
75
|
+
From a clone, run it on the test fixture with an AI agent action:
|
|
76
|
+
|
|
77
|
+
```sh
|
|
78
|
+
trust-path tests/fixtures/agent
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
```text
|
|
82
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 agent:anthropics/claude-code-action
|
|
83
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 permissions.issues:write
|
|
84
|
+
issues:event text read by agent .github/workflows/triage.yml triage anthropics/claude-code-action@v1 secrets.ANTHROPIC_API_KEY
|
|
85
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 agent:anthropics/claude-code-action
|
|
86
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 permissions.issues:write
|
|
87
|
+
issues:github.event.issue.body .github/workflows/triage.yml triage anthropics/claude-code-action@v1 secrets.ANTHROPIC_API_KEY
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
The workflow runs when an issue is opened and gives `anthropics/claude-code-action` the issue body
|
|
91
|
+
in its prompt, an API key and a token that can write issues. Anyone who can open an issue writes
|
|
92
|
+
that text, and the agent acts on it while holding the key and can write text into issues that
|
|
93
|
+
other workflows and agents read. Run `trust-path .` in a repository checkout to check its workflows.
|
|
94
|
+
|
|
95
|
+
## Documentation
|
|
96
|
+
|
|
97
|
+
- [How trust-path finds paths](https://github.com/jacob-adm/trust-path/blob/main/docs/model.md): sources, entry points, sinks, the AI agent action
|
|
98
|
+
list and the YAML subset.
|
|
99
|
+
- [Command](https://github.com/jacob-adm/trust-path/blob/main/docs/commands.md): output fields, JSON, exit status and an example across workflows.
|
|
100
|
+
- [Limitations and security](https://github.com/jacob-adm/trust-path/blob/main/docs/limitations-and-security.md): what trust-path does not see, read or do.
|
|
101
|
+
- [Using it with other tools](https://github.com/jacob-adm/trust-path/blob/main/docs/other-tools.md): a tested stack with git surface
|
|
102
|
+
and git-overlap, and what zizmor and poutine cover and what trust-path adds.
|
|
103
|
+
- [Contributing](https://github.com/jacob-adm/trust-path/blob/main/CONTRIBUTING.md): running the tests and contributing a change.
|
|
104
|
+
- [Reporting a vulnerability](https://github.com/jacob-adm/trust-path/blob/main/SECURITY.md)
|
|
105
|
+
|
|
106
|
+
## License
|
|
107
|
+
|
|
108
|
+
Apache License 2.0; see [LICENSE](https://github.com/jacob-adm/trust-path/blob/main/LICENSE).
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# SPDX-License-Identifier: Apache-2.0
|
|
2
|
+
[build-system]
|
|
3
|
+
requires = ["setuptools>=77"]
|
|
4
|
+
build-backend = "setuptools.build_meta"
|
|
5
|
+
|
|
6
|
+
[project]
|
|
7
|
+
name = "trust-path"
|
|
8
|
+
version = "0.1.0"
|
|
9
|
+
description = "List the paths by which untrusted input can reach secrets and publishing credentials in GitHub Actions workflows."
|
|
10
|
+
readme = "README.md"
|
|
11
|
+
requires-python = ">=3.9"
|
|
12
|
+
license = "Apache-2.0"
|
|
13
|
+
license-files = ["LICENSE"]
|
|
14
|
+
dependencies = []
|
|
15
|
+
keywords = ["github-actions", "security", "secrets", "ci", "supply-chain", "cli"]
|
|
16
|
+
classifiers = [
|
|
17
|
+
"Environment :: Console",
|
|
18
|
+
"Intended Audience :: Developers",
|
|
19
|
+
"Operating System :: OS Independent",
|
|
20
|
+
"Programming Language :: Python :: 3",
|
|
21
|
+
"Programming Language :: Python :: 3 :: Only",
|
|
22
|
+
"Topic :: Security",
|
|
23
|
+
]
|
|
24
|
+
|
|
25
|
+
[project.urls]
|
|
26
|
+
Homepage = "https://github.com/jacob-adm/trust-path"
|
|
27
|
+
Documentation = "https://github.com/jacob-adm/trust-path/tree/main/docs"
|
|
28
|
+
Source = "https://github.com/jacob-adm/trust-path"
|
|
29
|
+
Issues = "https://github.com/jacob-adm/trust-path/issues"
|
|
30
|
+
|
|
31
|
+
[project.scripts]
|
|
32
|
+
trust-path = "trust_path.cli:main"
|
|
33
|
+
|
|
34
|
+
[tool.setuptools]
|
|
35
|
+
packages = ["trust_path"]
|
|
File without changes
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
name: triage
|
|
2
|
+
on:
|
|
3
|
+
issues:
|
|
4
|
+
types: [opened]
|
|
5
|
+
permissions:
|
|
6
|
+
issues: write
|
|
7
|
+
jobs:
|
|
8
|
+
triage:
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
steps:
|
|
11
|
+
- uses: anthropics/claude-code-action@v1
|
|
12
|
+
with:
|
|
13
|
+
prompt: |
|
|
14
|
+
Label this issue:
|
|
15
|
+
${{ github.event.issue.body }}
|
|
16
|
+
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
name: build
|
|
2
|
+
on:
|
|
3
|
+
pull_request_target:
|
|
4
|
+
types: [opened, synchronize]
|
|
5
|
+
permissions:
|
|
6
|
+
contents: read
|
|
7
|
+
jobs:
|
|
8
|
+
build:
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
steps:
|
|
11
|
+
- uses: actions/checkout@v4
|
|
12
|
+
with:
|
|
13
|
+
ref: ${{ github.event.pull_request.head.sha }}
|
|
14
|
+
- name: Install
|
|
15
|
+
run: npm ci
|
|
16
|
+
env:
|
|
17
|
+
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
name: on comment
|
|
2
|
+
on: issue_comment
|
|
3
|
+
jobs:
|
|
4
|
+
reply:
|
|
5
|
+
permissions:
|
|
6
|
+
pull-requests: write
|
|
7
|
+
uses: ./.github/workflows/reply.yml
|
|
8
|
+
with:
|
|
9
|
+
text: ${{ github.event.comment.body }}
|
|
10
|
+
number: ${{ github.event.issue.number }}
|
|
11
|
+
secrets:
|
|
12
|
+
token: ${{ secrets.REPLY_TOKEN }}
|