.gitattributes

@@ -5,16 +5,20 @@
 # to LF line endings on checkout.
 *.afm text eol=lf
 *.cmap text eol=lf
-*.crt text eol=lf
 *.cs text eol=lf ident
+*.css text eol=lf
+*.htm text eol=lf
 *.html text eol=lf
 *.java text eol=lf ident
 *.lng text eol=lf
 *.md text eol=lf
 *.pom text eol=lf
 *.properties text eol=lf
+*.svg text eol=lf
 *.txt text eol=lf
 *.xfdf text eol=lf
+*.xht text eol=lf
+*.xhtml text eol=lf
 *.xml text eol=lf
 port-hash text eol=lf
 
@@ -24,21 +28,34 @@ port-hash text eol=lf
 *.sln text eol=crlf
 
 # Denote all files that are truly binary and should not be modified.
+*.aif binary
+*.aiff binary
 *.bmp binary
+*.cer binary
 *.cmp binary
+*.crt binary
 *.dib binary
 *.gif binary
+*.icc binary
 *.j2k binary
 *.jb2 binary
 *.jp2 binary
+*.jpc binary
 *.jpg binary
 *.key binary
 *.otf binary
+*.p12 binary
 *.pdf binary
 *.pfb binary
+*.pfm binary
 *.png binary
+*.snd binary
 *.tif binary
 *.tiff binary
 *.ttc binary
 *.ttf binary
+*.u3d binary
+*.wav binary
 *.wmf binary
+*.woff binary
+*.woff2 binary

.gitignore

@@ -222,3 +222,4 @@ $RECYCLE.BIN/
 target/
 nbactions*.xml
 src/core/iTextSharp.xml
+.idea/

.mailmap

@@ -0,0 +1,78 @@
+Alan Goo <alangoo@hancom.com>                                 <behumble@hanjava.net>
+Alexander Chingarev <alexander.chingarev@duallab.com>         <alexander.chingarev@itextpdf.com>
+Alexander Chingarev <alexander.chingarev@svaps.com>           <alexander.chingarev@gmail.com>
+Alexander Chingarev <alexander.chingarev@svaps.com>           <alexander.chingarev@svaps.com>
+Alexey Subach <alexey.subach@duallab.com>                     <alexey.subach@gmail.com>
+Alexey Subach <alexey.subach@duallab.com>                     <alexey.subach@itextpdf.com>
+Amedee Van Gasse <amedee.vangasse@itextpdf.com>               <amedee-github@amedee.be>
+Amedee Van Gasse <amedee.vangasse@itextpdf.com>               <amedee@vangasse.eu>
+Andrew Panfilov <andrew@panfilov.tel>                         <andrew@panfilov.tel>
+Bart De Meyer <bart@bartdemeyer.be>                           <bart@itextpdf.com>
+Benoît Lagae <benoit.lagae@itextpdf.com>                      <benoit@iText-blagae>
+Benoît Lagae <benoit.lagae@itextpdf.com>                      <benoit.lagae@itextpdf.com>
+Benoît Lagae <benoit.lagae@itextpdf.com>                      <benoit.lagae.s6547@student.hogent.be>
+Bruno Lowagie <bruno.lowagie@itextpdf.com>                    <bruno_000@192.168.1.3>
+Bruno Lowagie <bruno.lowagie@itextpdf.com>                    <bruno.lowagie@itextpdf.com>
+Bruno Lowagie <bruno.lowagie@itextpdf.com>                    <iText@Catullus>
+Bryan <bryan@hancom.com>                                      <bryan@192.168.152.124>
+Dimitry Alexandrov <dimzon541@gmail.com>                      <dimzon541@gmail.com>
+Dmitry Trusevich <dmitry.trusevich@duallab.com>               <dmitry.trusevich@duallab.com>
+Dmitry Trusevich <dmitry.trusevich@duallab>                   <dmitry.trusevich@duallab>
+Dominik Helm <dominik.helm@stud.tu-darmstadt.de>              <dominik.helm@stud.tu-darmstadt.de>
+gothinkfree <tyoh@hancom.com>                                 <tyoh@hancom.com>
+Ilya Idamkin <ilya.idamkin@duallab.com>                       <ilya.idamkin@TeamCity>
+iText Software <development@itextpdf.com>                     <community@itextpdf.com>
+iText Software <development@itextpdf.com>                     <development@itextpdf.com>
+iText Software <development@itextpdf.com>                     <jenkins@itextpdf.com>
+iText Software <development@itextpdf.com>                     <jenkins@jenkins.itextsupport.com>
+iText Software <development@itextpdf.com>                     <leeroy@itextpdf.com>
+iText Software <development@itextpdf.com>                     <teamcity.bot@TeamCity>
+iText Software <development@itextpdf.com>                     <teamcity@duallab.com>
+iText Software <development@itextpdf.com>                     <teamcity@itextpdf.com>
+Jeff Monson <jeff@advizr.co>                                  <jeff@advizr.co>
+Joris Schellekens <joris.schellekens@itextpdf.com>            <joris.schellekens@itextpdf.com>
+Kevin Day <kevin@trumpetinc.com>                              <kevin@melville.trumpetinc.local>
+Kevin Day <kevin@trumpetinc.com>                              <kevin@trumpetinc.com>
+Kevin Willems <kevin.willems@itextpdf.com>                    <kevin.willems1993@gmail.com>
+Kevin Willems <kevin.willems@itextpdf.com>                    <kevin.willems1993@gmail.com>
+LaughingMan <LingMan@users.noreply.github.com>                <LingMan@users.noreply.github.com>
+Markus Wernig <markus.wernig@xfer.ch>                         <markus.wernig@xfer.ch>
+Marvin Wichmann <marvin@fam-wichmann.de>                      <marvin@fam-wichmann.de>
+Marvin Wichmann <marvin.wichmann@fusion-hub.com>              <marvin.wichmann@fusion-hub.com>
+Marvin Wichmann <marvin.wichmann@unic.com>                    <marvin.wichmann@unic.com>
+Michaël Demey <michael.demey@itextpdf.com>                    michael.demey <>
+Michaël Demey <michael.demey@itextpdf.com>                    <michael.demey@itextpdf.com>
+Michaël Demey <michael.demey@itextpdf.com>                    <michael.demey@TeamCity>
+Michaël Demey <michael.demey@itextpdf.com>                    <mikkeldemey@gmail.com>
+Michael Glazunoff <michael.glazunoff@gmail.com>               <michael.glazunoff@gmail.com>
+Michael Klink <klink@csi.com>                                 <klink@csi.com>
+Michael Klink <mkl@wir-sind-cool.org>                         <mkl@wir-sind-cool.org>
+Nadia Ivaniukovich <nadia.ivaniuckovich@duallab.com>          <nadia.ivaniuckovich@duallab.com>
+Nadia Ivaniukovich <nadia.ivaniukovich@duallab.com>           <nadia.ivaniukovich@duallab.com>
+Nadja Sych <nadja.sych@duallab.com>                           <nadja.sych@duallab.com>
+Olivier Blaise <olivier@blaise.name>                          <olivier@blaise.name>
+Orabi Nakhla <orabi.nakhla@itextpdf.com>                      <orabi.nakhla@itextpdf.com>
+Orabi Nakhla <orabi.nakhla@itextpdf.com>                      <orabi.nakhleh@gmail.com>
+Paulo Soares <pgpsoares@gmail.com>                            <pgpsoares@gmail.com>
+Paulo Soares <psoares@gmail.com>                              <psoares@gmail.com>
+Pavel Alay <pavel.alay@duallab.com>                           pavel.alay <>
+Pavel Alay <pavel.alay@duallab.com>                           <pavel.alay@gmail.com>
+Pavel Alay <pavel.alay@duallab.com>                           <pavel.alay@TeamCity>
+Pavel Morozov <pavel.morozov@duallab.com>                     <pavel.morozov@duallab.com>
+Pavel Morozov <pavel.morozov@duallab.com>                     <p.morozov@i-pnt.ru>
+Peter Goodman <pete@petegoo.com>                              <github@petegoo.com>
+Peter Goodman <pete@petegoo.com>                              <pete@petegoo.com>
+Peter Goodman <pete@petegoo.com>                              <peter.goodman@pushpay.com>
+Peter Kjuak <peter.kjuak@itextpdf.com>                        <peter.kjuak@itextpdf.com>
+Richard Schwark <richard.schwark@planet.de>                   <richard.schwark@planet.de>
+Roman Leonov <roman.leonov@duallab.com>                       <roman.leonov@duallab.com>
+Roman Nadvodny <roman.nadvodniuk@duallab.com>                 <roman.nadvodniuk@duallab.com>
+Sasha Kalykhan <alexander.kalykhan@duallab.com>               <alexander.kalykhan@duallab.com>
+Sasha Kalykhan <alexander.kalykhan@duallab.com>               <alexanderkalykhan@gmail.com>
+Semen Yakushev <semen.yakushev@duallab.com>                   <semen.yakushev@duallab.com>
+Valera <7691262@mail.ru>                                      <7691262@mail.ru>
+Veronika Lisovskaya <veronika.lisovskaya@duallab.com>         <veronika.lisovskaya@TeamCity>
+Vit Nemecky <vit.nemecky@asseco-ce.com>                       <vit.nemecky@asseco-ce.com>
+Yanina Cheremisina <yanina.cheremisina@svaps.com>             <yanina.cheremisina@svaps.com>
+Yulian Gaponenko <yulian.gaponenko@duallab.com>               <duallab@DESKTOP-PG4L5J1>
+Yulian Gaponenko <yulian.gaponenko@duallab.com>               <yulian.gaponenko@TeamCity>

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to iText 7 Community
+# Contributing to iText Community
 
-We'd love for you to contribute to our source code and to make **iText 7 Community** even better than it is
+We'd love for you to contribute to our source code and to make **iText Community** even better than it is
 today! Here are the guidelines we'd like you to follow:
 
  - [Question or Problem?](#question)
@@ -15,7 +15,7 @@ today! Here are the guidelines we'd like you to follow:
 
 ## <a name="question">Got a Question or Problem?</a>
 
-If you have questions about how to use **iText 7 Community**, please direct these to [Stack Overflow][stackoverflow].
+If you have questions about how to use **iText Community**, please direct these to [Stack Overflow][stackoverflow].
 
 If you are a customer with a [support agreement][support], you also have direct access to our JIRA and our developers.
 
@@ -68,8 +68,7 @@ Before you submit your pull request consider the following guidelines:
 * Verify that your proposed change hasn't already been addressed in the develop branch.
 * Don't send a separate pull request for every single file you change.  
 * Please sign the [iText Contributor License Agreement (iCLA)](#cla) before sending pull
-  requests for any change of more than 20 significant lines of code (we're not counting curly braces and other syntactical sugar).
-  We cannot accept code without this agreement.
+  requests. We cannot accept code without this agreement.
 * Fork the iText repository on GitHub.
 * Clone your iText fork to your local machine.
 * Make your changes, **including appropriate test cases**.
@@ -80,7 +79,7 @@ Before you submit your pull request consider the following guidelines:
 * Build your changes locally to ensure all the tests pass.
 * Push your changes to your GitHub account.
 * Create a pull request in GitHub.
-"Head fork" should be your repository, and the "base fork" should be the iText7 official repository.
+"Head fork" should be your repository, and the "base fork" should be the iText official repository.
 * If we suggest changes then:
   * Make the required updates.
   * Fix up your commits if needed, with an interactive rebase.
@@ -100,8 +99,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 * We develop in Java first, and then port to .NET, so code submissions in Java are preferred.
   Nevertheless this shouldn't stop you from making a good pull request to the .NET port.
-* All Java code **must** be Java 7. Sorry, no lambda expressions or other Java 8 language features.
-* All features or bug fixes **must be tested** by one or more [unit tests][unit-testing].
+* All features or bug fixes **must be tested** by one or more unit tests.
 * All public API methods **must be documented** with JavaDoc. To see how we document our APIs, please check
   out the existing [javadocs][javadocs].
 * We follow the rules contained in
@@ -113,7 +111,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 We have guidelines on how our git commit messages should be formatted. This leads to **more
 readable messages** that are easy to follow when looking through the **project history**. But also,
-we use the git commit messages to **generate the iText 7 Community change log**.
+we use the git commit messages to **generate the iText Community change log**.
 
 These guidelines were taken from Chris Beams' blog post [How to Write a Git Commit Message][git-commit].
 
@@ -151,8 +149,7 @@ reference JIRA or GitHub issues that this commit **Closes**.
 
 ## <a name="cla">Signing the iCLA</a>
 
-Please sign the **iText Contributor License Agreement (iCLA)** before sending pull requests. For any larger code
-changes (more than 20 lines of significant code) to be accepted, the iCLA must be signed. It's a quick process, we promise!
+Please sign the [**iText Contributor License Agreement (iCLA)**][cla] before sending pull requests. For any code changes to be accepted, the iCLA must be signed. It's a quick process, we promise!
 
 We'll need you to [(digitally) sign and then email, fax or mail the form][cla].
 
@@ -165,18 +162,17 @@ We use the [Stack Exchange][stackoverflow] network for free support and [GitHub]
 * StackExchange: [http://stackexchange.com/legal](http://stackexchange.com/legal)
 * Github: [https://help.github.com/articles/github-terms-of-service/](https://help.github.com/articles/github-terms-of-service/)
 
-[cla]: http://itextpdf.com/policy
+[cla]: https://itextpdf.com/en/how-buy/legal/itext-contributor-license-agreement
 [coc]: CODE_OF_CONDUCT.md
-[github]: https://github.com/itext/itext7
-[java-style-guide]: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html
-[javadocs]: http://itextpdf.com/api
-[pull]: https://github.com/itext/itext7/pulls
+[github]: https://github.com/itext/i7n-pdfsweep
+[java-style-guide]: https://www.oracle.com/technetwork/java/codeconvtoc-136057.html
+[javadocs]: https://itextpdf.com/api
+[pull]: https://github.com/itext/i7n-pdfsweep/pulls
 [sscce]: http://sscce.org/
-[stackoverflow]: http://stackoverflow.com/questions/tagged/itext7
-[good-questions]: http://stackoverflow.com/help/how-to-ask
-[mcve]: http://stackoverflow.com/help/mcve
-[support]: http://itextpdf.com/support
-[unit-testing]: http://junit.org/
+[stackoverflow]: https://stackoverflow.com/questions/tagged/itext7
+[good-questions]: https://stackoverflow.com/help/how-to-ask
+[mcve]: https://stackoverflow.com/help/mcve
+[support]: https://itextpdf.com/support
 [git-commit]: https://chris.beams.io/posts/git-commit/
 [git-commit-separate]: https://chris.beams.io/posts/git-commit/#separate
 [git-commit-limit-50]: https://chris.beams.io/posts/git-commit/#limit-50

Jenkinsfile

@@ -0,0 +1,13 @@
+#!/usr/bin/env groovy
+@Library('pipeline-library')_
+
+def repoName = "pdfSweep"
+def dependencyRegex = "itextcore"
+def solutionFile = "itext.cleanup.sln"
+def frameworksToTest = "net461"
+
+withEnv(
+    ['ITEXT_VERAPDFVALIDATOR_ENABLE_SERVER=true', 
+     'ITEXT_VERAPDFVALIDATOR_PORT=8091']) {
+    automaticDotnetBuild(repoName, dependencyRegex, solutionFile, frameworksToTest)
+}

LICENSE.md

@@ -1,36 +1,16 @@
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License version 3
-    as published by the Free Software Foundation with the addition of the
-    following permission added to Section 15 as permitted in Section 7(a):
-    FOR ANY PART OF THE COVERED WORK IN WHICH THE COPYRIGHT IS OWNED BY
-    ITEXT GROUP. ITEXT GROUP DISCLAIMS THE WARRANTY OF NON INFRINGEMENT
-    OF THIRD PARTY RIGHTS
+    This program is offered under a commercial and under the AGPL license.
+    For commercial licensing, contact us at https://itextpdf.com/sales.  For AGPL licensing, see below.
 
-    This program is distributed in the hope that it will be useful, but
-    WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
-    or FITNESS FOR A PARTICULAR PURPOSE.
-    See the GNU Affero General Public License for more details.
-    You should have received a copy of the GNU Affero General Public License
-    along with this program; if not, see http://www.gnu.org/licenses or write to
-    the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
-    Boston, MA, 02110-1301 USA, or download the license from the following URL:
-    http://itextpdf.com/terms-of-use/
-
-    The interactive user interfaces in modified source and object code versions
-    of this program must display Appropriate Legal Notices, as required under
-    Section 5 of the GNU Affero General Public License.
+    AGPL licensing:
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
 
-    In accordance with Section 7(b) of the GNU Affero General Public License,
-    a covered work must retain the producer line in every PDF that is created
-    or manipulated using iText.
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
 
-    You can be released from the requirements of the license by purchasing
-    a commercial license. Buying such a license is mandatory as soon as you
-    develop commercial activities involving the iText software without
-    disclosing the source code of your own applications.
-    These activities include: offering paid services to customers as an ASP,
-    serving PDFs on the fly in a web application, shipping iText with a closed
-    source product.
-
-    For more information, please contact iText Software Corp. at this
-    address: sales@itextpdf.com
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.

README.md

@@ -1,6 +1,6 @@
-**[pdfSweep][pdfSweep]** is an [iText 7][itext] add on.
+**[pdfSweep][pdfSweep]** is an [iText][itext] add on.
 
-This add on will allow you to easily construct e-Sweeps. As of yet, the only supported format is the ZUGFeRD standard. Support for other formats is on the way. Should you want to add support to a format then we invite you to take a look at our [Contribution Guidelines][contributing].
+This add on will allow you to easily redact PDF files. Redaction is the process of removing sensitive or confidential information. pdfSweep will remove this data entirely so that it won't be extractable anymore.
 
 The **pdfSweep Community** source code is hosted on [Github][github], where you can also [download the latest releases][latest].
 

SECURITY.md

@@ -0,0 +1,40 @@
+# iText Security Policy
+
+## Reporting a Vulnerability
+
+We are committed to maintaining the security of our software. If you discover a security vulnerability, we encourage you to report it to us as soon as possible.
+
+To report a vulnerability, please visit our [Vulnerability Reporting Page](https://itextpdf.com/report-vulnerability), or email [vulnerability@apryse.com](vulnerability@apryse.com). If you do not receive a response in 2 business days, please follow up as we may not have received your message.
+
+We follow the procedure of Coordinated Vulnerability Disclosure (CVD) and, to protect the ecosystem, we request that those reporting do the same. Please visit the above page for more information, and follow the steps below to ensure that your report is handled promptly and appropriately:
+
+1. **Do not disclose the vulnerability publicly** until we have had a chance to address it.
+2. **Provide a detailed description** of the vulnerability, including steps to reproduce it, if possible.
+3. **Include any relevant information** such as the version of pdfSweep you are using, your operating system, and any other pertinent details.
+
+## Security Updates and Patches
+
+ When a vulnerability is reported, we will:
+
+1. **Investigate and verify** the vulnerability.
+2. **Develop and test** a fix for the vulnerability.
+3. **Release a patch** as soon as possible.
+
+
+## Known Vulnerabilities
+
+The iText Knowledge Base has a page for known [Common Vulnerabilities and Exposures](https://kb.itextpdf.com/itext/cves) (CVEs), please check it to ensure your vulnerability has not already been disclosed or addressed.
+
+## Supported product lines
+
+See [Compatibility Matrix](https://kb.itextpdf.com/itext/compatibility-matrix)
+
+## Security Best Practices
+
+To help ensure the security of your applications using pdfSweep, we recommend the following best practices:
+
+1. **Keep pdfSweep up to date** by regularly checking for and applying updates.
+2. **Review and follow** our security guidelines for secure usage.
+3. **Monitor your applications** for any unusual activity and investigate any anomalies promptly.
+
+Thank you for helping us keep iText secure!