Case file No.289 · pypi · stdio

openroles

io.github.aranculleton/openroles · v0.2.0

Open roles from employers' own job boards: Greenhouse, Lever, Ashby, Workday and 12 more.

Package ↗GitHub ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 1 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

425 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v0.1.2 → v0.2.0Oct 20, 2026

version changed version bump
```
"0.1.2" → "0.2.0"
```

description changed description text edit

"Open roles from any employer's Greenhouse, Lever, Ashby or Workday board. No API key." → "Open roles from employers' own job boards: Greenhouse, Lever, Ashby, Workday and 12 more."

packages.0.version changed package version bump
```
"0.1.2" → "0.2.0"
```

First snapshot (v0.1.2)Oct 18, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is openroles safe?

MCPWatch gives openroles a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does openroles have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package openroles. That is not proof of safety.

When was openroles last updated?

The latest registry version is 0.2.0, published Oct 19, 2026. The last push to aranculleton/openroles was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does openroles use?

GitHub reports the license of aranculleton/openroles as MIT.

Related servers

same publisher / similar score