appinspect | Splunk App 's compliance with Splunk

by splunkdevabhi Python Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | appinspect Summary

appinspect is a Python library. appinspect has no bugs, it has no vulnerabilities, it has build file available and it has low support. However appinspect has a Non-SPDX License. You can download it from GitHub.

AppInspect is a tool for assessing a Splunk App's compliance with Splunk recommended development practices, by using static analysis. AppInspect is open for extension, allowing other teams to compose checks that meet their domain specific needs for semi- or fully-automated analysis and validation of Splunk Apps.

Support

Quality

Security

License

Reuse

Support

appinspect has a low active ecosystem.

It has 2 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

appinspect has no issues reported. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of appinspect is current.

Quality

appinspect has no bugs reported.

Security

appinspect has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

appinspect has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

appinspect releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed appinspect and discovered the below as its top functions. This is intended to give you an instant insight into appinspect implemented functionality, and help decide if they suit your requirements.

Ensures that the default source type is present in the config file .
Generate a report for each check .
Validate an app package .
Check if the web . conf file contains restmap patterns .
Return a list of Command objects .
Check for binary files without source code .
Run the Splunk application .
Check if setup is available in distribution .
Check to see if formatter html in the template .
Returns AlertAction instances .

Get all kandi verified functions for this library.

appinspect Key Features

No Key Features are available at this moment for appinspect.

appinspect Examples and Code Snippets

No Code Snippets are available at this moment for appinspect.

Community Discussions

No Community Discussions are available at this moment for appinspect.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install appinspect

Checkout the development branch
Create and activate a virtual env
Build and install from source pip install -r (windows|darwin|linux).txt, it depends on your system platform python setup.py install That's it. The splunk-appinspect tool is installed into your virtualenv. You can verify this by running the following commands: splunk-appinspect splunk-appinspect list version
Create a distribution of AppInspect python setup.py sdist after running the above command, an installation package with name like splunk-appinspect-<version>.tar.gz is created under the dist folder
Install the distro previously created pip install dist/splunk-appinspect-<version>.tar.gz
Each update in VERSION.txt should correspond to a package release:.
Install the latest AppInspect CLI from the development branch. wget -r -l1 --no-parent --no-directories -A 'splunk-appinspect-*.tar.gz' https://repo.splunk.com/artifactory/Solutions/AppInspect/CLI/develop/builds/latest/ && pip install splunk-appinspect-*.tar.gz
If we aim for a major release, we should name the version referring semver as is, example: 1.6.0.
If we aim for a hotfix release, we should append hotfix version to current version({appinspect version}+b{hotfix version}), example: 1.6.0+b1. Note: if there is a second hotfix after the first hotfix, the version should be updated to 1.6.0+b2, and so on.
If we aim for a rc build in release-candidate phase, we should append rc version({appinspect version}rc{hotfix version}), example: 1.6.0rc2.