awsfindingsmanagerlib 0.0.0__tar.gz

awsfindingsmanagerlib-0.0.0/.VERSION

@@ -0,0 +1 @@
+0.0.0

awsfindingsmanagerlib-0.0.0/AUTHORS.rst

@@ -0,0 +1,14 @@
+=======
+Credits
+=======
+
+Development Lead
+----------------
+
+* Tyfoxylos Costas <ctyfoxylos@schubergphilis.com>
+
+
+Contributors
+------------
+
+* Marwin Baumann <mbaumann@schubergphilis.com>

awsfindingsmanagerlib-0.0.0/CONTRIBUTING.rst

@@ -0,0 +1,45 @@
+============
+Contributing
+============
+
+Contributions are welcome, and they are greatly appreciated! Every
+little bit helps, and credit will always be given.
+
+Submit Feedback
+~~~~~~~~~~~~~~~
+
+If you are proposing a feature:
+
+* Explain in detail how it would work.
+* Keep the scope as narrow as possible, to make it easier to implement.
+
+Get Started!
+------------
+
+Ready to contribute? Here's how to set up `awsfindingsmanagerlib` for local development.
+Using of pipenv is highly recommended.
+
+1. Clone your fork locally::
+
+    $ git clone git@github.com:schubergphilis/awsfindingsmanagerlib.git
+
+2. Install your local copy into a virtualenv. Assuming you have pipenv installed, this is how you set up your clone for local development::
+
+    $ cd awsfindingsmanagerlib/
+    $ pipenv install --ignore-pipfile
+
+3. Create a branch for local development::
+
+    $ git checkout -b name-of-your-bugfix-or-feature
+
+   Now you can make your changes locally.
+   Do your development while using the CI capabilities and making sure the code passes lint, test, build and document stages.
+
+
+4. Commit your changes and push your branch to the server::
+
+    $ git add .
+    $ git commit -m "Your detailed description of your changes."
+    $ git push origin name-of-your-bugfix-or-feature
+
+5. Submit a merge request

awsfindingsmanagerlib-0.0.0/HISTORY.rst

@@ -0,0 +1,4 @@
+.. :changelog:
+
+History
+-------

awsfindingsmanagerlib-0.0.0/LICENSE

@@ -0,0 +1,200 @@
+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:
+
+    You must give any other recipients of the Work or Derivative Works a copy of
+     this License; and
+
+    You must cause any modified files to carry prominent notices stating that
+     You changed the files; and
+
+    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
+
+    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.
+
+
+
+

awsfindingsmanagerlib-0.0.0/MANIFEST.in

@@ -0,0 +1,18 @@
+include .VERSION
+include AUTHORS.rst
+include CONTRIBUTING.rst
+include HISTORY.rst
+include LICENSE
+include README.rst
+include USAGE.rst
+include Pipfile
+include Pipfile.lock
+include requirements.txt
+include dev-requirements.txt
+include awsfindingsmanagerlib/.VERSION
+
+recursive-exclude * __pycache__
+recursive-exclude * *.py[co]
+
+recursive-include docs *.rst conf.py Makefile
+recursive-include awsfindingsmanagerlib *

awsfindingsmanagerlib-0.0.0/PKG-INFO

@@ -0,0 +1,104 @@
+Metadata-Version: 2.1
+Name: awsfindingsmanagerlib
+Version: 0.0.0
+Summary: A library to manage findings in AWS.
+Home-page: https://github.com/schubergphilis/awsfindingsmanagerlib.git
+Author: Marwin Baumann
+Author-email: mbaumann@schubergphilis.com
+License: Apache Software License 2.0
+Keywords: awsfindingsmanagerlib securityhub findings aws
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3.8
+License-File: LICENSE
+License-File: AUTHORS.rst
+Requires-Dist: boto3>=1.34.92; python_version >= "3.8"
+Requires-Dist: opnieuw>=1.2.1; python_version >= "3.7"
+Requires-Dist: python-dateutil>=2.9.0.post0; python_version >= "2.7" and python_version not in "3.0, 3.1, 3.2, 3.3"
+Requires-Dist: schema~=0.7.5
+Requires-Dist: requests~=2.31.0; python_version >= "3.7"
+Requires-Dist: pyyaml~=6.0.1; python_version >= "3.6"
+
+=====================
+awsfindingsmanagerlib
+=====================
+
+A library to manage findings in AWS.
+
+
+* Documentation: https://awsfindingsmanagerlib.readthedocs.org/en/latest
+
+
+Development Workflow
+====================
+
+The workflow supports the following steps
+
+ * lint
+ * test
+ * build
+ * document
+ * upload
+ * graph
+
+These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
+Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.
+
+The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
+It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project
+
+Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
+So for the initial delivery one would call
+
+    $ _tag --minor
+
+which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.
+
+
+So the full workflow after git is initialized is:
+
+ * repeat as necessary (of course it could be test - code - lint :) )
+
+   * code
+   * lint
+   * test
+ * commit and push
+ * develop more through the code-lint-test cycle
+ * tag (with the appropriate argument)
+ * build
+ * upload (if you want to host your package in pypi)
+ * document (of course this could be run at any point)
+
+
+Important Information
+=====================
+
+This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
+So when building a package out of this **do not** simple call
+
+    $ python setup.py sdist
+
+**as this will produce an unusable artifact with files missing.**
+Instead use the provided build and upload scripts that create all the necessary files in the artifact.
+
+
+
+Project Features
+================
+
+* TODO
+
+
+
+License info
+============
+
+While the project is released under the Apache 2 license, scripts under _CI/scripts are released under an MIT license as stated on their header.
+
+
+
+
+History
+-------

awsfindingsmanagerlib-0.0.0/Pipfile

@@ -0,0 +1,30 @@
+[[source]]
+url = "https://pypi.python.org/simple"
+verify_ssl = true
+name = "pypi"
+
+[dev-packages]
+sphinx = ">=7.0,<8.0"
+sphinx-rtd-theme = ">=1.0,<2.0"
+prospector = ">=1.8,<2.0"
+coverage = ">=7,<8.0"
+nose = ">=1.3,<2.0"
+nose-htmloutput = ">=0.1,<1.0"
+tox = ">=4.0<5.0"
+betamax = ">=0.8,<1.0"
+betamax-serializers = "~=0.2,<1.0"
+semver = ">=3.0,<4.0"
+gitwrapperlib = ">=1.0,<2.0"
+twine = ">=4.0,<5.0"
+coloredlogs = ">=15.0,<16.0"
+emoji = ">=2.0,<3.0"
+toml = ">=0.1,<1.0"
+typing-extensions = ">=4.0,<5.0"
+
+[packages]
+boto3 = ">=1.19.8,<2.0"
+opnieuw = ">=1.1.0,<2.0"
+python-dateutil = ">=2.8.2,<3.0"
+schema = "*"
+requests = "*"
+pyyaml = "*"