An independent package manager for unix and linux๐ท
## Table of contents ๐
* [`Why`](#why)
* [`Features`](#features)
* [`Installation`](#installation)
* [`Hysp usages`](#usages)
* [`Hosting custom repo`](#repo)
* [`Packages`](#pkgs)
* [`Support`](#support)
* [`License`](#license)
## Why?? ๐ฉ
I am a **CTF player** [***(Capture the flag)*** ](https://en.wikipedia.org/wiki/Capture_the_flag_(cybersecurity)) who often finds myself without my main laptop in places that lack the tools I need. Some distros don't carry the packages I require and some doesn't keep them updated. That's why I created my own package manager :). It fetches tool binaries easily, ensuring I always have what I need to compete.
Dont touch my shrug
## Features โพ
1. **Versatile** : Hysp operates on (*nix) systems and various architectures (x86, aarch64_arm), providing flexibility for your needs.
2. **Simple** : No prerequisites is needed for `Hysp` or `hysp-pkgs`. Install Hysp as a single binary, no need for Go, Rust, or any other dependencies. Saves space, storage, and time.
3. **Customizable** : Pkg-Source can be self-hosted by anyone, allowing hysp to use your ***very own*** instead of the default source and local configuration as well. See [#Self hosting](https://github.com/pwnwriter/hysp#repo)
4. **Statically compiled** : The default source [`metis-os/hysp-pkgs`](https://github.com/metis-os/hysp-pkgs)) has all statically compiled binaries, _only statically linked binaries that will run anywhere_. You can always host dynamic or whatever you want.
5. **No Special Privileges** : [Hysp](https://github.com/pwnwriter/hysp) requires no special perms or privileges. It can run completely in userspace with all of its features.
6. **Everything is open source** : Hysp uses github actions to build and ship the packages. On top of that it uses `sha` for varifying the binary.
7. Security Considerations
It is never a good idea to install random binaries from random sources.
Check these `HackerNews Discussions`
> - [A cautionary tale from the decline of SourceForge](https://news.ycombinator.com/item?id=31110206)
> - [Downloading PuTTY Safely Is Nearly Impossible (2014)](https://news.ycombinator.com/item?id=9577861)
> ```bash
> !# PKG Metadata
> # Everything is automated via Github Actions & Scripts
> Repo --> https://github.com/metis-os/hysp-pkgs
> WorkFlows --> https://github.com/metis-os/hysp-pkgs/tree/main/.github/workflows
> Scripts --> https://github.com/metis-os/hysp-pkgs/tree/main/.github/scripts
>
> !# Upstream Source
> # Everything is automated via Github Actions & Build Scripts
> Repo --> https://github.com/Azathothas/Toolpacks
> WorkFlows --> https://github.com/Azathothas/Toolpacks/tree/main/.github/workflows
> Build Scripts --> https://github.com/Azathothas/Toolpacks/tree/main/.github/scripts
> ```
## Installation ๐ฉ
###### ๐ค From source
```bash
git clone --depth=1 https://github.com/pwnwriter/hysp --branch=main
cd hysp
cargo build --release
```
Then go to `release` dir and `./hysp` or move the `binary` to your any `$PATH` for instant access from anywhere.
๐ช Binary
- *Manual* : You can directly download the [**binary**](https://github.com/pwnwriter/hysp/releases) of your arch and run it.
- *One liner* : Run this script, requires `jq`,`curl`, `tar` & `wget`
```bash
wget -qO- "$(curl -qfsSL "https://api.github.com/repos/pwnwriter/hysp/releases/latest" | jq -r '.assets[].browser_download_url' | grep -Ei "$(uname -m).*$(uname -s).*musl" | grep -v "\.sha")" | tar -xzf - --strip-components=1
./hysp -h
```
๐ฎ using Cargo
- Using [crates.io](https://crates.io/crates/hysp)
```bash
cargo install hysp
```
- Using [binstall](https://github.com/cargo-bins/cargo-binstall)
```bash
cargo binstall hysp
```
> **NOTE:**
> This requires a working setup of rust/cargo & binstall.
๐ฉ METIS Linux
```bash
sudo/doas pacman -Sy hysp
```
๐ข Arch user repository
```bash
paru/yay -S hysp-git
```
## Hysp usages ๐
***Firstly, if you intend to access the binaries installed via `hysp` over the system, you may want to...***
##### Setup path for hysp bin
- Add the following line to your shellrc. [ `zshrc`, `bashrc` ***etc***. ]
```bash
export PATH="$HOME/.local/share/hysp/bin/:$PATH"
```
Help menu
```bash
hysp |install|uninstall|search| -h # check for help menu
```
Installing packages
```bash
hysp install -p # use --force to overwrite already installed binary, --quiet to supress console io
```
Removing packages
```bash
hysp remove -p
```
Search for available pkgs
```bash
hysp search -p
```
- Raw mode (default)
- Database mode
- Fuzzy mode
Checking configuration health
```bash
hysp health
```
##### Numerous other options exist. Consider installing Hysp and checking it out, wouldn't you?
## Hosting custom repo ๐พ
- Hysp provies the following configuration, which can be overwritten by defining a `config file` in `~/.config/hysp/config.toml`
```toml
[source]
remote = "https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/x86_64"
metadata ="https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/metadata.toml"
aarch = "Architecture"
[local]
home="/home/user/.local/share/hysp"
bin="/home/user/.local/share/hysp/bin/"
data="/home/user/.local/share/hysp/data/"
```
- Explanation
| Name | Description | Default |
|-------------|------------------------------------|----------------------------------------------------|
| `remote` | Package repository | [***`metis-os/hysp-pkgs`***](https://github.com/metis-os/hysp-pkgs) |
| `metadata` | Available pkg info | [***`metis-os/hysp-pkgs/metadata.toml`***](https://raw.githubusercontent.com/metis-os/hysp-pkgs/main/data/metadata.toml)|
| `home` | Home for `hysp` | ***`hysp`*** |
| `bin` | Directory to save the binaries | ***`~/.local/share/hysp/bin`*** |
| `data` | Directory to save pkg data | ***`~/.local/share/hysp/data`*** |
| `aarch` | Your system Architecture | Only supported ***`X86_64,aarch64`*** |
๐ Tree view of the repo
```bash
.
โโโ available.toml # Storing available pkgs info (Optional)
โโโ data
โย โโโ foo.toml # where the package data are stored (needed)
```
๐ Sample pkg
```bash
[bin]
name = "$BIN" # Name of the pkg to be installed as
[package]
architecture = "x86_64" # Your aarchitecture
name = "$BIN" # Your package name
description = "$DESCRIPTION" # Description
author = "$AUTHOR" # Author
repo = "$REPO_URL"
stars = "${STARS}"
version = "$PKG_VERSION"
updated = "$PKG_RELEASED"
size = "$SIZE"
sha = "$SHA"
source = "$SOURCE_URL" # Source of the binary wherever it's hosted
language = "$LANGUAGE"
license = "$LICENSE"
[package.conditions]
conflicts = ["$BIN"] # Conflictions
requires = [] # Dependencies
[package.metadata]
keywords = $TOPICS
categories = ["Utilities"]
```
## Packages whuat?? ๐ฆ
There is a list of packages available in [*`metis-os/hysp-pkgs`*](https://github.com/metis-os/hysp-pkgs) . You can confidently utilize the default configuration without any hesitation. However, if you prefer to host your own packages, you have the option to do so by creating your own custom configuration file under ***`~/.config/hysp/config.toml`***. See [`#repo`](https://github.com/pwnwriter/hysp#repo)
## Support ๐
I am a student currently attending university. I like working for *Open Source* in my free time. If you find my tool or work beneficial, please consider supporting me via [*KO-FI*](https://ko-fi.com/pwnwriter) or [*ESEWA*](https://metislinux.org/docs/donate)* (***Nepal only***), Or by leaving a star โญ ; I'll appreciate your action :)
## License ใ๏ธ
Everything is license under the [`MIT`](https://raw.githubusercontent.com/pwnwriter/hysp/main/LICENSE) except for the packages...
They hold their own livess :oOO
Copyright © 2023 pwnwriter xyz โ๏ธ