flagrante 0.0.1__tar.gz

flagrante-0.0.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

flagrante-0.0.1/PKG-INFO

@@ -0,0 +1,153 @@
+Metadata-Version: 2.4
+Name: flagrante
+Version: 0.0.1
+Summary: Which of your components carry vulnerabilities confirmed exploited in the wild -- the ones that start a CRA Article 14 24-hour reporting clock
+Author: Flagrante
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://flagrante.dev
+Project-URL: Source, https://github.com/pacordelcw/flagrante
+Project-URL: Issues, https://github.com/pacordelcw/flagrante/issues
+Project-URL: Changelog, https://github.com/pacordelcw/flagrante/commits/main
+Keywords: cra,cyber-resilience-act,article-14,sbom,cyclonedx,spdx,kev,epss,osv,vulnerability,compliance,eu
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: Legal Industry
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# flagrante
+
+**Which of your components start a CRA Article 14 24-hour clock.**
+
+Since 11 September 2026, a manufacturer placing a product with digital elements
+on the EU market must send an early warning within **24 hours** of becoming
+aware that a vulnerability in that product is **actively exploited**.
+
+Every SBOM scanner on the market tells you which components are *vulnerable*.
+That is not the question Article 14 asks. Thousands of CVEs are vulnerabilities;
+a few hundred are being exploited. Only the second group starts a clock.
+
+`flagrante` makes that distinction the whole output.
+
+```
+24-HOUR CLOCK LIKELY RUNNING  (2)
+  Confirmed exploited in the wild -- CISA KEV
+
+  CVE-2021-44228  org.apache.logging.log4j/log4j-core@2.14.1
+      listed in CISA KEV since 2021-12-10 as exploited in the wild, linked to ransomware campaigns
+
+ASSESS TODAY  (16)
+  Elevated exploitation probability, not yet confirmed
+  ...
+
+VERDICT
+  1 component carries 2 vulnerabilities confirmed exploited in the wild. If any
+  of these ship in a product you place on the EU market, assess Article 14
+  reporting now.
+
+ARTICLE 14 CASCADE
+  Early warning     2026-09-04 17:10 UTC   (24h)
+  Notification      2026-09-06 17:10 UTC   (72h)
+  Final report      2026-09-17 17:10 UTC   (14d)
+```
+
+## Use it
+
+You need an SBOM. If you do not have one, generate it free — `flagrante` does not
+duplicate that job, because [syft](https://github.com/anchore/syft) and
+[cdxgen](https://github.com/CycloneDX/cdxgen) already do it well.
+
+```bash
+pip install flagrante
+syft dir:. -o cyclonedx-json | flagrante
+```
+
+Or against a file, in CI, or as JSON:
+
+```bash
+flagrante sbom.json
+flagrante sbom.json --json > result.json
+flagrante sbom.json --all          # include findings with no exploitation signal
+flagrante sbom.json --fail-on urgent
+```
+
+Exit codes: `0` nothing at the chosen level, `1` confirmed exploited,
+`2` urgent (with `--fail-on urgent`), `3` the scan could not complete.
+
+### GitHub Action
+
+```yaml
+- uses: actions/checkout@v4
+- run: syft dir:. -o cyclonedx-json > sbom.json
+- uses: pacordelcw/flagrante@v1
+  with:
+    sbom: sbom.json
+    fail-on: exploited
+```
+
+## How it decides
+
+Three public feeds, no API keys:
+
+| Feed | Answers |
+|---|---|
+| [OSV](https://osv.dev) | which components carry known vulnerabilities |
+| [CISA KEV](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) | which CVEs are **confirmed exploited in the wild** |
+| [FIRST EPSS](https://www.first.org/epss/) | probability of exploitation within 30 days |
+
+| Tier | Trigger |
+|---|---|
+| **24-hour clock likely running** | CVE listed in CISA KEV |
+| **Assess today** | EPSS ≥ 10%, not in KEV |
+| **Track** | known vulnerability, no exploitation signal |
+| **Cannot be checked** | no package URL in the SBOM |
+
+## What this is not
+
+`flagrante` is an **exposure indicator**. It is not a conformity assessment, not
+legal advice, and not a determination that no reporting obligation exists.
+
+Three limits worth stating plainly, because a tool in this space that hides
+them is not worth trusting:
+
+1. **It cannot tell whether vulnerable code is reachable in your product.**
+   A KEV match means the CVE is exploited somewhere in the world, not that
+   *your* product is being attacked. Article 14 turns on the vulnerability
+   being in the product and actively exploited. That judgement is yours.
+
+2. **"Actively exploited" is not perfectly determinable from public data.**
+   KEV lags real-world exploitation, and EPSS is a model, not an observation.
+   Absence of a signal here is not evidence of absence in the world.
+
+3. **There is deliberately no "you are compliant" outcome.** Over-flagging
+   costs you an afternoon; under-flagging costs up to €15 million or 2.5% of
+   global turnover. Every threshold in this tool is set by that asymmetry, and
+   there is a test suite that fails the build if a future change ever softens
+   the wording into reassurance.
+
+If a feed is unreachable, `flagrante` refuses to print a result rather than
+printing an empty one — an unreachable exploitation feed and a clean scan look
+identical and mean opposite things.
+
+## Development
+
+No dependencies, no network in the test suite:
+
+```bash
+python -m unittest discover -s tests
+```
+
+Apache-2.0.

flagrante-0.0.1/README.md

@@ -0,0 +1,123 @@
+# flagrante
+
+**Which of your components start a CRA Article 14 24-hour clock.**
+
+Since 11 September 2026, a manufacturer placing a product with digital elements
+on the EU market must send an early warning within **24 hours** of becoming
+aware that a vulnerability in that product is **actively exploited**.
+
+Every SBOM scanner on the market tells you which components are *vulnerable*.
+That is not the question Article 14 asks. Thousands of CVEs are vulnerabilities;
+a few hundred are being exploited. Only the second group starts a clock.
+
+`flagrante` makes that distinction the whole output.
+
+```
+24-HOUR CLOCK LIKELY RUNNING  (2)
+  Confirmed exploited in the wild -- CISA KEV
+
+  CVE-2021-44228  org.apache.logging.log4j/log4j-core@2.14.1
+      listed in CISA KEV since 2021-12-10 as exploited in the wild, linked to ransomware campaigns
+
+ASSESS TODAY  (16)
+  Elevated exploitation probability, not yet confirmed
+  ...
+
+VERDICT
+  1 component carries 2 vulnerabilities confirmed exploited in the wild. If any
+  of these ship in a product you place on the EU market, assess Article 14
+  reporting now.
+
+ARTICLE 14 CASCADE
+  Early warning     2026-09-04 17:10 UTC   (24h)
+  Notification      2026-09-06 17:10 UTC   (72h)
+  Final report      2026-09-17 17:10 UTC   (14d)
+```
+
+## Use it
+
+You need an SBOM. If you do not have one, generate it free — `flagrante` does not
+duplicate that job, because [syft](https://github.com/anchore/syft) and
+[cdxgen](https://github.com/CycloneDX/cdxgen) already do it well.
+
+```bash
+pip install flagrante
+syft dir:. -o cyclonedx-json | flagrante
+```
+
+Or against a file, in CI, or as JSON:
+
+```bash
+flagrante sbom.json
+flagrante sbom.json --json > result.json
+flagrante sbom.json --all          # include findings with no exploitation signal
+flagrante sbom.json --fail-on urgent
+```
+
+Exit codes: `0` nothing at the chosen level, `1` confirmed exploited,
+`2` urgent (with `--fail-on urgent`), `3` the scan could not complete.
+
+### GitHub Action
+
+```yaml
+- uses: actions/checkout@v4
+- run: syft dir:. -o cyclonedx-json > sbom.json
+- uses: pacordelcw/flagrante@v1
+  with:
+    sbom: sbom.json
+    fail-on: exploited
+```
+
+## How it decides
+
+Three public feeds, no API keys:
+
+| Feed | Answers |
+|---|---|
+| [OSV](https://osv.dev) | which components carry known vulnerabilities |
+| [CISA KEV](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) | which CVEs are **confirmed exploited in the wild** |
+| [FIRST EPSS](https://www.first.org/epss/) | probability of exploitation within 30 days |
+
+| Tier | Trigger |
+|---|---|
+| **24-hour clock likely running** | CVE listed in CISA KEV |
+| **Assess today** | EPSS ≥ 10%, not in KEV |
+| **Track** | known vulnerability, no exploitation signal |
+| **Cannot be checked** | no package URL in the SBOM |
+
+## What this is not
+
+`flagrante` is an **exposure indicator**. It is not a conformity assessment, not
+legal advice, and not a determination that no reporting obligation exists.
+
+Three limits worth stating plainly, because a tool in this space that hides
+them is not worth trusting:
+
+1. **It cannot tell whether vulnerable code is reachable in your product.**
+   A KEV match means the CVE is exploited somewhere in the world, not that
+   *your* product is being attacked. Article 14 turns on the vulnerability
+   being in the product and actively exploited. That judgement is yours.
+
+2. **"Actively exploited" is not perfectly determinable from public data.**
+   KEV lags real-world exploitation, and EPSS is a model, not an observation.
+   Absence of a signal here is not evidence of absence in the world.
+
+3. **There is deliberately no "you are compliant" outcome.** Over-flagging
+   costs you an afternoon; under-flagging costs up to €15 million or 2.5% of
+   global turnover. Every threshold in this tool is set by that asymmetry, and
+   there is a test suite that fails the build if a future change ever softens
+   the wording into reassurance.
+
+If a feed is unreachable, `flagrante` refuses to print a result rather than
+printing an empty one — an unreachable exploitation feed and a clean scan look
+identical and mean opposite things.
+
+## Development
+
+No dependencies, no network in the test suite:
+
+```bash
+python -m unittest discover -s tests
+```
+
+Apache-2.0.

flagrante-0.0.1/flagrante/__init__.py

@@ -0,0 +1,26 @@
+"""flagrante -- which of your components start a CRA Article 14 24-hour clock."""
+
+__version__ = "0.0.1"
+
+from .classify import Assessment, Finding, Tier, assess, early_warning_fields
+from .sbom import Component, SBOMDocument, SBOMError, parse, parse_file
+from .scan import scan_document, scan_file, scan_text
+from .sources import FeedError
+
+__all__ = [
+    "Assessment",
+    "Component",
+    "FeedError",
+    "Finding",
+    "SBOMDocument",
+    "SBOMError",
+    "Tier",
+    "assess",
+    "early_warning_fields",
+    "parse",
+    "parse_file",
+    "scan_document",
+    "scan_file",
+    "scan_text",
+    "__version__",
+]