stegguard 0.4.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.
- stegguard-0.4.0/LICENSE +201 -0
- stegguard-0.4.0/NOTICE +4 -0
- stegguard-0.4.0/PKG-INFO +356 -0
- stegguard-0.4.0/README.md +314 -0
- stegguard-0.4.0/pyproject.toml +91 -0
- stegguard-0.4.0/setup.cfg +4 -0
- stegguard-0.4.0/stegguard/__init__.py +25 -0
- stegguard-0.4.0/stegguard/__main__.py +9 -0
- stegguard-0.4.0/stegguard/_version.py +4 -0
- stegguard-0.4.0/stegguard/cli.py +192 -0
- stegguard-0.4.0/stegguard/common.py +36 -0
- stegguard-0.4.0/stegguard/detector.py +3909 -0
- stegguard-0.4.0/stegguard/integrations.py +393 -0
- stegguard-0.4.0/stegguard/limits.py +144 -0
- stegguard-0.4.0/stegguard/operations.py +315 -0
- stegguard-0.4.0/stegguard/reporting.py +46 -0
- stegguard-0.4.0/stegguard/robust.py +315 -0
- stegguard-0.4.0/stegguard/schema.py +4 -0
- stegguard-0.4.0/stegguard/schemas/report-v1.schema.json +32 -0
- stegguard-0.4.0/stegguard/watermark.py +1035 -0
- stegguard-0.4.0/stegguard.egg-info/PKG-INFO +356 -0
- stegguard-0.4.0/stegguard.egg-info/SOURCES.txt +41 -0
- stegguard-0.4.0/stegguard.egg-info/dependency_links.txt +1 -0
- stegguard-0.4.0/stegguard.egg-info/entry_points.txt +2 -0
- stegguard-0.4.0/stegguard.egg-info/requires.txt +16 -0
- stegguard-0.4.0/stegguard.egg-info/top_level.txt +1 -0
- stegguard-0.4.0/tests/test_benchmarks.py +54 -0
- stegguard-0.4.0/tests/test_demo.py +87 -0
- stegguard-0.4.0/tests/test_detector.py +2428 -0
- stegguard-0.4.0/tests/test_fuzz_inputs.py +36 -0
- stegguard-0.4.0/tests/test_html_report_local.py +209 -0
- stegguard-0.4.0/tests/test_integrations.py +385 -0
- stegguard-0.4.0/tests/test_license_metadata.py +38 -0
- stegguard-0.4.0/tests/test_operations.py +241 -0
- stegguard-0.4.0/tests/test_path_portability.py +52 -0
- stegguard-0.4.0/tests/test_provenance_regressions.py +102 -0
- stegguard-0.4.0/tests/test_public_contracts.py +70 -0
- stegguard-0.4.0/tests/test_reliability_contract.py +276 -0
- stegguard-0.4.0/tests/test_repository_readiness.py +218 -0
- stegguard-0.4.0/tests/test_resource_limits.py +276 -0
- stegguard-0.4.0/tests/test_robust_media.py +143 -0
- stegguard-0.4.0/tests/test_structural.py +78 -0
- stegguard-0.4.0/tests/test_watermark.py +529 -0
stegguard-0.4.0/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
stegguard-0.4.0/NOTICE
ADDED
stegguard-0.4.0/PKG-INFO
ADDED
|
@@ -0,0 +1,356 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: stegguard
|
|
3
|
+
Version: 0.4.0
|
|
4
|
+
Summary: Detect, decode, and safely remove hidden content and provenance signals
|
|
5
|
+
Author: Aditya Arakeri
|
|
6
|
+
Maintainer: Aditya Arakeri
|
|
7
|
+
License-Expression: Apache-2.0
|
|
8
|
+
Project-URL: Source, https://github.com/stegguard/stegguard
|
|
9
|
+
Project-URL: Documentation, https://github.com/stegguard/stegguard/tree/main/docs
|
|
10
|
+
Project-URL: Issues, https://github.com/stegguard/stegguard/issues
|
|
11
|
+
Project-URL: Security, https://github.com/stegguard/stegguard/security/policy
|
|
12
|
+
Keywords: steganography,detection,security,llm,nlp
|
|
13
|
+
Classifier: Development Status :: 3 - Alpha
|
|
14
|
+
Classifier: Intended Audience :: Developers
|
|
15
|
+
Classifier: Intended Audience :: Science/Research
|
|
16
|
+
Classifier: Programming Language :: Python :: 3
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
20
|
+
Classifier: Operating System :: OS Independent
|
|
21
|
+
Classifier: Topic :: Security
|
|
22
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
23
|
+
Requires-Python: <3.15,>=3.12
|
|
24
|
+
Description-Content-Type: text/markdown
|
|
25
|
+
License-File: LICENSE
|
|
26
|
+
License-File: NOTICE
|
|
27
|
+
Provides-Extra: images
|
|
28
|
+
Requires-Dist: Pillow>=12.0.0; extra == "images"
|
|
29
|
+
Provides-Extra: dev
|
|
30
|
+
Requires-Dist: bandit>=1.8; extra == "dev"
|
|
31
|
+
Requires-Dist: build>=1.2; extra == "dev"
|
|
32
|
+
Requires-Dist: check-wheel-contents>=0.6; extra == "dev"
|
|
33
|
+
Requires-Dist: hypothesis>=6.0; extra == "dev"
|
|
34
|
+
Requires-Dist: mypy>=1.15; extra == "dev"
|
|
35
|
+
Requires-Dist: pip-audit>=2.9; extra == "dev"
|
|
36
|
+
Requires-Dist: pygments>=2.20.0; extra == "dev"
|
|
37
|
+
Requires-Dist: pytest>=9.0.3; extra == "dev"
|
|
38
|
+
Requires-Dist: pytest-cov; extra == "dev"
|
|
39
|
+
Requires-Dist: ruff>=0.12; extra == "dev"
|
|
40
|
+
Requires-Dist: twine>=6.0; extra == "dev"
|
|
41
|
+
Dynamic: license-file
|
|
42
|
+
|
|
43
|
+
# StegGuard
|
|
44
|
+
|
|
45
|
+
<p align="center">
|
|
46
|
+
<img src="https://raw.githubusercontent.com/stegguard/stegguard/main/images/steg_banner.png" alt="StegGuard: Uncovering Hidden Data" width="630">
|
|
47
|
+
</p>
|
|
48
|
+
|
|
49
|
+
**Find what is hiding in plain sight.**
|
|
50
|
+
|
|
51
|
+
[](https://www.python.org/)
|
|
52
|
+
[](https://github.com/stegguard/stegguard/blob/main/LICENSE)
|
|
53
|
+
[](https://github.com/stegguard/stegguard/blob/main/pyproject.toml)
|
|
54
|
+
|
|
55
|
+
StegGuard is a local-first toolkit for finding, decoding, and safely removing
|
|
56
|
+
hidden content from files. It looks beyond ordinary metadata and scans for
|
|
57
|
+
invisible Unicode, whitespace channels, homoglyphs, suspicious media
|
|
58
|
+
structures, watermark signals, fingerprints, and Content Credentials.
|
|
59
|
+
|
|
60
|
+
It runs on the Python standard library, stays offline by default, and explains
|
|
61
|
+
what it found in JSON and HTML reports you can actually hand to another person.
|
|
62
|
+
|
|
63
|
+
StegGuard is alpha software. Treat its findings as investigative evidence, not
|
|
64
|
+
as an infallible verdict.
|
|
65
|
+
|
|
66
|
+
## See it work
|
|
67
|
+
|
|
68
|
+
The repository includes a deterministic, harmless demo. It hides the word
|
|
69
|
+
`DEMO` in zero-width characters, detects and decodes it, writes a sanitized
|
|
70
|
+
copy, verifies the result, and analyzes a synthetic PNG for watermark and
|
|
71
|
+
provenance signals.
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
python3 demo/run_demo.py
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
Expected ending:
|
|
78
|
+
|
|
79
|
+
```text
|
|
80
|
+
Demo completed successfully
|
|
81
|
+
Decoded hidden text: DEMO
|
|
82
|
+
Original preserved: True
|
|
83
|
+
Reports: .../demo-output/reports
|
|
84
|
+
Summary: .../demo-output/summary.json
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
The demo makes no network requests and contains no executable or malicious
|
|
88
|
+
payload. Open `demo-output/reports/detect.html` after the run to inspect the
|
|
89
|
+
report. See [the demo guide](https://github.com/stegguard/stegguard/blob/main/demo/README.md) for every generated artifact.
|
|
90
|
+
|
|
91
|
+
## Why StegGuard exists
|
|
92
|
+
|
|
93
|
+
Hidden content is rarely one neat payload in one neat format. It can be a
|
|
94
|
+
zero-width message in a prompt, a Cyrillic character in a source file, trailing
|
|
95
|
+
spaces in a document, bytes after a media container, a private PNG chunk, or a
|
|
96
|
+
provenance claim that exists but has never been cryptographically validated.
|
|
97
|
+
|
|
98
|
+
Most tools handle one of those cases. StegGuard gives them a shared workflow:
|
|
99
|
+
|
|
100
|
+
```text
|
|
101
|
+
untrusted file -> detect -> inspect -> decode -> sanitize a copy -> verify
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
The original stays untouched unless you explicitly authorize an in-place
|
|
105
|
+
replacement.
|
|
106
|
+
|
|
107
|
+
## Install
|
|
108
|
+
|
|
109
|
+
When a release is available on PyPI:
|
|
110
|
+
|
|
111
|
+
```bash
|
|
112
|
+
python3 -m pip install stegguard
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
From source:
|
|
116
|
+
|
|
117
|
+
```bash
|
|
118
|
+
git clone https://github.com/stegguard/stegguard.git
|
|
119
|
+
cd stegguard
|
|
120
|
+
python3 -m pip install -e .
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
StegGuard requires Python 3.12 or newer and has no mandatory runtime
|
|
124
|
+
dependencies.
|
|
125
|
+
|
|
126
|
+
For wider image-format decoding through the explicitly tested Pillow path:
|
|
127
|
+
|
|
128
|
+
```bash
|
|
129
|
+
python3 -m pip install "stegguard[images]"
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
The supported Python range is 3.12 through 3.14. CI is configured for Linux,
|
|
133
|
+
macOS, and Windows; hosted results are required before those targets are
|
|
134
|
+
described as verified. Architecture details and current evidence are in
|
|
135
|
+
[docs/platform-support.md](https://github.com/stegguard/stegguard/blob/main/docs/platform-support.md).
|
|
136
|
+
|
|
137
|
+
## Quick start
|
|
138
|
+
|
|
139
|
+
Scan one file:
|
|
140
|
+
|
|
141
|
+
```bash
|
|
142
|
+
stegguard detect suspicious.py
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
Scan a repository and save both report formats:
|
|
146
|
+
|
|
147
|
+
```bash
|
|
148
|
+
stegguard detect ./repo -r --json findings.json --html report.html
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
Decode recognized text-carried channels without modifying the source:
|
|
152
|
+
|
|
153
|
+
```bash
|
|
154
|
+
stegguard decode suspicious.txt
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
Write a sanitized copy and receive hashes, change counts, and a unified diff:
|
|
158
|
+
|
|
159
|
+
```bash
|
|
160
|
+
stegguard sanitize suspicious.txt
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
Analyze watermark and provenance signals:
|
|
164
|
+
|
|
165
|
+
```bash
|
|
166
|
+
stegguard watermark image.png --json watermark.json --html watermark.html
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
Validate Content Credentials with the official `c2patool` executable:
|
|
170
|
+
|
|
171
|
+
```bash
|
|
172
|
+
stegguard watermark image.png --c2pa-tool c2patool --html provenance.html
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
## Commands
|
|
176
|
+
|
|
177
|
+
| Command | What it does |
|
|
178
|
+
| --- | --- |
|
|
179
|
+
| `stegguard detect` | Scans files or directories for hidden-content signals |
|
|
180
|
+
| `stegguard decode` | Extracts recognized text-carried payloads without changing the input |
|
|
181
|
+
| `stegguard sanitize` | Writes a safer copy and reports every change |
|
|
182
|
+
| `stegguard watermark` | Analyzes watermark, fingerprint, and provenance evidence |
|
|
183
|
+
|
|
184
|
+
Run `stegguard COMMAND --help` for command-specific options.
|
|
185
|
+
|
|
186
|
+
For `detect`, exit status `0` means a completed clean scan, `1` means a
|
|
187
|
+
completed scan with findings, and `2` means invalid input or an incomplete
|
|
188
|
+
scan. The complete compatibility contract is in
|
|
189
|
+
[docs/compatibility.md](https://github.com/stegguard/stegguard/blob/main/docs/compatibility.md).
|
|
190
|
+
|
|
191
|
+
## What it detects
|
|
192
|
+
|
|
193
|
+
### Text and source files
|
|
194
|
+
|
|
195
|
+
- Zero-width and invisible Unicode characters
|
|
196
|
+
- Bidirectional controls and suspicious formatting characters
|
|
197
|
+
- Cyrillic and Greek homoglyphs
|
|
198
|
+
- Trailing-space and tab channels, including SNOW-style patterns
|
|
199
|
+
- Mixed and encoded line-ending patterns
|
|
200
|
+
- Repeated punctuation, spacing, and layout intervals
|
|
201
|
+
|
|
202
|
+
### Images, audio, and structured media
|
|
203
|
+
|
|
204
|
+
- Pixel-level LSB anomalies as a distinct detection category
|
|
205
|
+
- Transform and block-correlation signals in decodable lossless images
|
|
206
|
+
- Phase, echo, spectral, spread-spectrum, and silence-interval statistics in
|
|
207
|
+
PCM WAV audio
|
|
208
|
+
- PNG metadata, private chunks, and appended data
|
|
209
|
+
- JPEG EXIF, XMP, and IPTC indicators
|
|
210
|
+
- RIFF trailing data, ISO BMFF private boxes, and PSD structures
|
|
211
|
+
- Pluggable analyzers for compressed codecs, keyed schemes, and video
|
|
212
|
+
|
|
213
|
+
### Documents and containers
|
|
214
|
+
|
|
215
|
+
- PDF embedded files and active or hidden structures
|
|
216
|
+
- DOCX, PPTX, XLSX, ZIP, and compatible archive members
|
|
217
|
+
- Nested media and archives with bounded member and decompression limits
|
|
218
|
+
- SVG and HTML comments, hidden styles, and external references
|
|
219
|
+
|
|
220
|
+
### Watermarks and provenance
|
|
221
|
+
|
|
222
|
+
- Metadata, structural, text-pattern, and layout evidence
|
|
223
|
+
- Robust image, audio, and video signal families
|
|
224
|
+
- Device, camera, printer, encoder, and codec fingerprints
|
|
225
|
+
- Embedded and sidecar C2PA manifests
|
|
226
|
+
- Content Credentials validated through `c2patool`
|
|
227
|
+
- External manifest references with opt-in, bounded HTTPS retrieval
|
|
228
|
+
- Pluggable AI text-watermark verifiers
|
|
229
|
+
|
|
230
|
+
Detection categories remain separate in the output. An LSB anomaly is not
|
|
231
|
+
reported as a robust watermark, and the presence of a C2PA manifest is not
|
|
232
|
+
reported as cryptographic validation.
|
|
233
|
+
|
|
234
|
+
## Sanitization is deliberately cautious
|
|
235
|
+
|
|
236
|
+
By default, this command:
|
|
237
|
+
|
|
238
|
+
```bash
|
|
239
|
+
stegguard sanitize suspicious.txt
|
|
240
|
+
```
|
|
241
|
+
|
|
242
|
+
writes `suspicious.sanitized.txt`. It will not overwrite an existing output and
|
|
243
|
+
it reports:
|
|
244
|
+
|
|
245
|
+
- SHA-256 hashes before and after
|
|
246
|
+
- A unified text diff
|
|
247
|
+
- Counts for every normalization
|
|
248
|
+
- Whether the original was preserved
|
|
249
|
+
- Provenance status before and after
|
|
250
|
+
- Whether a content change invalidated provenance
|
|
251
|
+
|
|
252
|
+
Overwriting the original requires both flags:
|
|
253
|
+
|
|
254
|
+
```bash
|
|
255
|
+
stegguard sanitize suspicious.txt --in-place --confirm
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
Unsupported binary formats are copied byte-for-byte and marked
|
|
259
|
+
`NO_OP_UNSUPPORTED`. StegGuard does not push binary data through a text cleaner
|
|
260
|
+
and hope for the best.
|
|
261
|
+
|
|
262
|
+
## Reports built for review
|
|
263
|
+
|
|
264
|
+
JSON findings are machine-readable, JSON-compatible, and designed for downstream tools.
|
|
265
|
+
HTML reports include:
|
|
266
|
+
|
|
267
|
+
- Executive severity and provenance summaries
|
|
268
|
+
- Per-file evidence with locations and confidence
|
|
269
|
+
- Nested container findings
|
|
270
|
+
- Signer, source type, manifest location, and validation errors
|
|
271
|
+
- C2PA actions, timestamps, edits, and ingredients
|
|
272
|
+
- Clear disclaimers around authorship and missing watermarks
|
|
273
|
+
|
|
274
|
+
Valid provenance is informational. Tampered or untrusted provenance raises the
|
|
275
|
+
reported risk.
|
|
276
|
+
|
|
277
|
+
Machine-readable reports carry `schema_version`. The supported schema is
|
|
278
|
+
packaged at `stegguard/schemas/report-v1.schema.json` and its evolution policy
|
|
279
|
+
is documented in [docs/compatibility.md](https://github.com/stegguard/stegguard/blob/main/docs/compatibility.md).
|
|
280
|
+
|
|
281
|
+
## Python API
|
|
282
|
+
|
|
283
|
+
The core workflows are also available as Python functions:
|
|
284
|
+
|
|
285
|
+
```python
|
|
286
|
+
from stegguard import analyze_file, decode_file, sanitize_file, scan_file
|
|
287
|
+
|
|
288
|
+
detection = analyze_file("suspicious.txt")
|
|
289
|
+
decoded = decode_file("suspicious.txt")
|
|
290
|
+
sanitized = sanitize_file("suspicious.txt")
|
|
291
|
+
watermarks = scan_file("image.png")
|
|
292
|
+
```
|
|
293
|
+
|
|
294
|
+
Each function returns JSON-compatible data.
|
|
295
|
+
|
|
296
|
+
## Trust and network model
|
|
297
|
+
|
|
298
|
+
StegGuard does not make unsolicited network requests. Remote C2PA manifests are
|
|
299
|
+
disabled unless `--allow-remote-manifests` is supplied. When enabled, retrieval
|
|
300
|
+
is HTTPS-only, rejects redirects and non-global addresses, and enforces timeout
|
|
301
|
+
and response-size limits.
|
|
302
|
+
|
|
303
|
+
C2PA states are explicit: `VALID`, `TAMPERED`, `UNTRUSTED_SIGNER`, `MISSING`,
|
|
304
|
+
`UNSUPPORTED`, or `NOT_CHECKED`. If cryptographic validation did not happen,
|
|
305
|
+
StegGuard says so.
|
|
306
|
+
|
|
307
|
+
Scans have configurable limits for input bytes, decompression, image pixels,
|
|
308
|
+
archive members, nesting depth, elapsed time, and retained findings. See
|
|
309
|
+
[docs/resource-limits.md](https://github.com/stegguard/stegguard/blob/main/docs/resource-limits.md) before processing uploads or
|
|
310
|
+
running StegGuard as a service.
|
|
311
|
+
|
|
312
|
+
## Current limitations
|
|
313
|
+
|
|
314
|
+
- `c2patool` is optional and installed separately. Without a validator, an
|
|
315
|
+
embedded C2PA claim remains `NOT_CHECKED`.
|
|
316
|
+
- Keyed and proprietary watermark schemes require their corresponding analyzer.
|
|
317
|
+
- Generic robust-media statistics are leads, not cryptographic proof.
|
|
318
|
+
- Video and compressed-codec analysis require a configured analyzer. Missing
|
|
319
|
+
analysis is reported as `NOT_CHECKED`, not clean.
|
|
320
|
+
- No official Anthropic text-watermark verifier is bundled. StegGuard does not
|
|
321
|
+
replace one with a home-grown guess.
|
|
322
|
+
- Valid provenance means an asset passed the configured validation. It does not
|
|
323
|
+
prove authorship. A missing mark does not prove human authorship either.
|
|
324
|
+
|
|
325
|
+
## Development
|
|
326
|
+
|
|
327
|
+
```bash
|
|
328
|
+
git clone https://github.com/stegguard/stegguard.git
|
|
329
|
+
cd stegguard
|
|
330
|
+
uv run pytest
|
|
331
|
+
uv run pytest --cov=stegguard --cov-report=term-missing
|
|
332
|
+
uv run ruff check stegguard tests demo scripts benchmarks
|
|
333
|
+
```
|
|
334
|
+
|
|
335
|
+
The project intentionally keeps its runtime dependency-free. Tests may use
|
|
336
|
+
development dependencies declared in `pyproject.toml`. Contributor setup,
|
|
337
|
+
fixture safety, review expectations, and all local gates are in
|
|
338
|
+
[CONTRIBUTING.md](https://github.com/stegguard/stegguard/blob/main/CONTRIBUTING.md).
|
|
339
|
+
|
|
340
|
+
## Contributing
|
|
341
|
+
|
|
342
|
+
Bug reports, new fixtures, detector improvements, and careful false-positive
|
|
343
|
+
reports are welcome. Please include a minimal reproducible sample generated at
|
|
344
|
+
test time. Do not commit suspicious payloads, credentials, or generated reports.
|
|
345
|
+
|
|
346
|
+
Open an issue or pull request at
|
|
347
|
+
[github.com/stegguard/stegguard](https://github.com/stegguard/stegguard).
|
|
348
|
+
|
|
349
|
+
Project policies: [security](https://github.com/stegguard/stegguard/blob/main/SECURITY.md), [support](https://github.com/stegguard/stegguard/blob/main/SUPPORT.md),
|
|
350
|
+
[governance](https://github.com/stegguard/stegguard/blob/main/GOVERNANCE.md), [releases](https://github.com/stegguard/stegguard/blob/main/RELEASING.md),
|
|
351
|
+
[detection quality](https://github.com/stegguard/stegguard/blob/main/docs/detection-quality.md), and [changelog](https://github.com/stegguard/stegguard/blob/main/CHANGELOG.md).
|
|
352
|
+
|
|
353
|
+
## License
|
|
354
|
+
|
|
355
|
+
StegGuard is licensed under Apache License 2.0. See [LICENSE](https://github.com/stegguard/stegguard/blob/main/LICENSE) and
|
|
356
|
+
[NOTICE](https://github.com/stegguard/stegguard/blob/main/NOTICE).
|