You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release mostly provides important changes in the backend part that will be supported in the UI in the next releases.
7
+
* Analyzable: Representation of an observable or a sample: every job is linked to the scanned analyzable.
8
+
* Data models: A new system to normalize the output of analyzers (already available in the job raw section). It allows analyzers to specify the evaluation, reliability and many others information about the analyzable.
9
+
* User Event: Users can create reports for analyzables: indicating additional information or a custom evaluation.
10
+
* Engine: Evaluate user reports and analyzers's data to assign a score to the job.
11
+
12
+
As usual, we add new plugins. This release brings the following new ones:
13
+
*[Nuclei](https://github.com/projectdiscovery/nuclei): A modern, high-performance vulnerability scanner that leverages simple YAML-based templates.
14
+
*[ipquery](https://ipquery.io/): a flexible api for vpn detection, geolocation, and threat intelligence.
15
+
*[mullvad](https://mullvad.net/en): VPN provider.
16
+
*[spamhaus](https://www.spamhaus.org/): Updated existing analyzer to support IPv6.
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,11 +25,13 @@ Please delete options that are not relevant.
25
25
-[ ] If you created a new analyzer and it is free (does not require any API key), please add it in the `FREE_TO_USE_ANALYZERS` playbook by following [this guide](https://intelowlproject.github.io/docs/IntelOwl/contribute/#how-to-modify-a-plugin).
26
26
-[ ] Check if it could make sense to add that analyzer/connector to other [freely available playbooks](https://intelowlproject.github.io/docs/IntelOwl/usage/#list-of-pre-built-playbooks).
27
27
-[ ] I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
28
-
-[ ] If the plugin interacts with an external service, I have created an attribute called precisely `url` that contains this information. This is required for Health Checks.
28
+
-[ ] If the plugin interacts with an external service, I have created an attribute called precisely `url` that contains this information. This is required for Health Checks (HEAD HTTP requests).
29
29
-[ ] If the plugin requires mocked testing, `_monkeypatch()` was used in its class to apply the necessary decorators.
30
30
-[ ] I have added that raw JSON sample to the `MockUpResponse` of the `_monkeypatch()` method. This serves us to provide a valid sample for testing.
31
+
-[ ] I have created the corresponding `DataModel` for the new analyzer following the [documentation](https://intelowlproject.github.io/docs/IntelOwl/contribute/#how-to-create-a-datamodel)
31
32
-[ ] I have inserted the copyright banner at the start of the file: ```# This file is a part of IntelOwl https://github.com/intelowlproject/IntelOwl # See the file 'LICENSE' for copying permission.```
32
-
-[ ] If external libraries/packages with restrictive licenses were used, they were added in the [Legal Notice](https://github.com/certego/IntelOwl/blob/master/.github/legal_notice.md) section.
33
+
-[ ] Please avoid adding new libraries as requirements whenever it is possible. Use new libraries only if strictly needed to solve the issue you are working for. In case of doubt, ask a maintainer permission to use a specific library.
34
+
-[ ] If external libraries/packages with restrictive licenses were added, they were added in the [Legal Notice](https://github.com/certego/IntelOwl/blob/master/.github/legal_notice.md) section.
33
35
-[ ] Linters (`Black`, `Flake`, `Isort`) gave 0 errors. If you have correctly installed [pre-commit](https://intelowlproject.github.io/docs/IntelOwl/contribute/#how-to-start-setup-project-and-development-instance), it does these checks and adjustments on your behalf.
34
36
-[ ] I have added tests for the feature/bug I solved (see `tests` folder). All the tests (new and old ones) gave 0 errors.
Copy file name to clipboardExpand all lines: .github/workflows/stale.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,8 @@ jobs:
19
19
stale-pr-label: "stale"
20
20
exempt-pr-labels: "keep-open"
21
21
# Issues
22
-
stale-issue-message: "This issue has been marked as stale because it has had no activity for 10 days. If you are still working on this, please provide some updates."
23
-
days-before-issue-stale: 10
22
+
stale-issue-message: "This issue has been marked as stale because it has had no activity for 30 days. If you are still working on this, please provide some updates."
0 commit comments