IntelOwl
IntelOwl copied to clipboard
PhoneInfoga#995
closes #995
Description
Add phoneinfoga_scan analyzer
Type of change
Please delete options that are not relevant.
- [ ] Bug fix (non-breaking change which fixes an issue).
- [x] New feature (non-breaking change which adds functionality).
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
Checklist
- [x] I have read and understood the rules about how to Contribute to this project
- [x] The pull request is for the branch
develop
- [x] A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
- [x] I strictly followed the documentation "How to create a Plugin"
- [x] Usage file was updated.
- [x] Advanced-Usage was updated (in case the plugin provides additional optional configuration).
- [x] If the plugin requires mocked testing,
_monkeypatch()
was used in its class to apply the necessary decorators. - [x] I have dumped the configuration from Django Admin using the
dumpplugin
command and added it in the project as a data migration. ("How to share a plugin with the community") - [x] If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive
test_files.zip
and you added the default tests for that mimetype in test_classes.py. - [x] If you created a new analyzer and it is free (does not require API keys), please add it in the
FREE_TO_USE_ANALYZERS
playbook by following this guide. - [x] Check if it could make sense to add that analyzer/connector to other freely available playbooks.
- [x] I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
- [x] If external libraries/packages with restrictive licenses were used, they were added in the Legal Notice section.
- [x] Linters (
Black
,Flake
,Isort
) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf. - [x] I have added tests for the feature/bug I solved (see
tests
folder). All the tests (new and old ones) gave 0 errors. - [x] If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
- [ ] If the GUI has been modified:
- [ ] I have a provided a screenshot of the result in the PR.
- [ ] I have created new frontend tests for the new component or updated existing ones.
Important Rules
- If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
- If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
- Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.
raw json: {"result":{"valid":true,"number":"33679368229","local_format":"0679368229","international_format":"+33679368229","country_prefix":"+33","country_code":"FR","country_name":"France","location":"","carrier":"Orange France SA","line_type":"mobile"}}