semvec/pypi-packages huggingface dataset:
zulip-doc 0.4.0
Zulip service that checks user presence for Duty of Care responsibilities for remote teams
License: MIT
Requires Python: >=3.8

# Zulip Duty of Care Service

A small script to check user presence in Zulip. If a user hasn't been around for a while it will send you a message in Zulip so you can check up on them and see if they are ok.

## Install

`pipx install zulip-doc`

## Usage

```
Usage: zdoc [OPTIONS] [SEND_TO]...

Arguments:
  [SEND_TO]...

Options:
  --max-idle INTEGER              [env var: MAX_IDLE; default: 86400]
  --ignore-weekends / --no-ignore-weekends
                                  [env var: IGNORE_WEEKENDS; default: ignore-
                                  weekends]
  --config-file FILE              [env var: CONFIG_FILE; default:
                                  /home/{username}/.zuliprc]
  --help                          Show this message and exit.
```

Example: `zdoc 12 22`


## Cron Job Setup

`crontab -e`

Then add something like:

`0 12 * * * /home/paul/.local/bin/zdoc --config-file /home/paul/.zuliprc 12 22`

*runs everyday at noon*
hoppr-nexus-bundler 0.5.2
Plug-in for Hoppr to bundle artifacts into a Nexus Repository
License: MIT
Requires Python: >=3.10,<4.0
Keywords: hoppr,plugin,nexus

# Nexus Bundler for Hoppr

The Nexus Bundler is a plug-in for [Hoppr](https://gitlab.com/lmco/hoppr/hoppr) to package the collected artifacts into an existing Nexus instance.

## Configuration

The following fields are supported values for configuring this plugin (in the Hoppr transfer configuration file):


| Option | Description | Default |
| ------ | ------ |------|
|url| The URL for the Nexus API | Port 8081 on the server specified by the NEXUS_IP environment variable, using an `http://` schema |
|username| User name to be used to access the Nexus instance | `admin` |
|password_env| Envirionment variable containing the password to access the Nexus instance with the above username | `NEXUS_PW`|
|docker_url| URL to be used to access the docker repository on the Nexus instance. | Port 5000 on the server specified by the NEXUS_IP environment variable, using an `http://` schema |
|docker_port| Port on which the Nexus instance should listen for docker requests | `5000` |
|force_http| Indicates whether docker requests should be accessed using the `http://` or `https://` url schema.  |`False` (docker requests must be made using `https://`) |

**Note**: At this time, the Nexus Bundler only supports a single Docker repository per Nexus instance

**Note**: The port of the `docker_url` may differ from that specified by `docker_port` because of port forwarding (for example, if Nexus is run as a docker image).  `docker_port` is the port used internally by Nexus.

For example, if Nexus is run as a docker image via `docker run -p 1701:5000 sonatype/nexus3:3.40.1` then the  `docker_port` would be `5000`, and the `docker_url` would be something like `https://myserver.com:1701/`.
hoppr-jq-filter 0.2.1
Starter Plug-in for Hoppr
License: MIT
Requires Python: >=3.10,<4.0
Keywords: hoppr,plugin,packaging,reports,build dependencies,software bill of materials

# Hoppr JQ Filter

A Hoppr plugin to filter components out of the delivered sbom using jq syntax.

It works as the intersect of "includes" and "excludes".

- Any components not found with the includes will be removed
- Any components found with the excludes will be removed

```yml
  SampleStage:
    plugins:
    - name: "hoppr_jq_filter.plugin"
      config:
        delete_excluded: True
        purl_regex_includes: []
        purl_regex_excludes: []
        jq_expression_includes: []
        jq_expression_excludes: []
```

- `delete_excluded`
  - A flag indicating if the plugin should delete any excluded components found in `collect_root_dir`
- `purl_regex_includes`
  - A list of regular expressions for purls that should remain in the SBOM
- `purl_regex_excludes`
  - A list of regular expressions to remove purls that match in the SBOM
- `jq_expression_includes`
  - A list of jq expressions for components that should remain in the SBOM
- `jq_expression_excludes`
  - A list of jq expressions to remove components that match in the SBOM

## Examples

### Only keep generic components in the SBOM

```yml
  SampleStage:
    plugins:
    - name: "hoppr_jq_filter.plugin"
      config:
        purl_regex_includes:
          - "^pkg:generic"
```

### Remove any purl with `controlled` in the name

```yml
  SampleStage:
    plugins:
    - name: "hoppr_jq_filter.plugin"
      config:
        purl_regex_excludes:
          - "controlled"
```

## Debugging

If you are having trouble filtering out components, you can easily debug using `jq` directly.

1. Run hoppr bundle with a `-v` and review the logs.
1. This plugin will print all of the jq queries used and the matching purls found.
1. You can `cat your-sbom.cdx.json | jq '<your query>'` to debug.