carpe-pytsk | pytsk is a Python binding for the SleuthKit

by dfrc-korea Python Version: Current License: Non-SPDX

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

kandi X-RAY | carpe-pytsk Summary

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

pytsk is a Python binding for the SleuthKit. The SleuthKit is a complete filesystem analysis tool. In the past PyFlag shipped a Python binding for a statically compiled version which was incorporated in the PyFlag source tree (Version 2.78). That version is now very old and does not support HFS+ which SleuthKit 3.1 does. At the time there were some important functions that we needed to link to but the old libtsk (the shared object produced by older SleuthKit binaries) did not export these - which is the reason for incorporating a slightly modified version in the source tree. These days things are much better - libtsk is designed to be a general purpose library with many useful functions linked in. The overall architecture has been tremendously improved and it is now very easy to use it from an external program.

Support

Quality

Security

License

Reuse

Support

carpe-pytsk has a low active ecosystem.

It has 20 star(s) with 5 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

carpe-pytsk has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of carpe-pytsk is current.

Quality

carpe-pytsk has 0 bugs and 0 code smells.

Security

carpe-pytsk has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

carpe-pytsk code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

carpe-pytsk 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

carpe-pytsk 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.

carpe-pytsk saves you 2189 person hours of effort in developing the same functionality from scratch.

It has 4792 lines of code, 396 functions and 18 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

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

Command - line entry point
List a directory tree
Open a directory
Print a directory entry
Write local variables to out
Find optional default variables
Writes builtins
Return a generator of all attributes
Runs sleuthkit
Generate Python bindings
Clone self
Return the error condition
Define constants
Write the prototype
Write the module to a file
Returns a string representation of the node
Prepare Enum
Write the documentation for this method
Class constructor
Write GetSetDef to out
Generate Python bindings for source files
Read data from the file
Create a proxy class
Runs the script
Write the getter
Build the source files

Get all kandi verified functions for this library.

carpe-pytsk Key Features

No Key Features are available at this moment for carpe-pytsk.

carpe-pytsk Examples and Code Snippets

No Code Snippets are available at this moment for carpe-pytsk.

Community Discussions

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

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

Vulnerabilities

No vulnerabilities reported

Install carpe-pytsk

You can download it from GitHub.
You can use carpe-pytsk like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: