Sn1per
1N3/Sn1per
Automated penetration testing & attack surface management platform. Recon, scan, exploit, report — 600+ exploits, 90+ integrations, 10K+ detections.
Ship status
SlowedLast push 31–120 days ago. Quiet, not gone.
- Last push
- Jul 4, 2026
- 99 days ago
- Stars, last 7 weeks
- History starts 2026-09-22, the first weekly sample after this repo joined the directory.
Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.
Repo facts
What GitHub reports.
- Stars
- 11.4K
- Forks
- 2.2K
- Open issues
- 9
- Watchers
- 345
- Primary language
- Shell
- License
- Other
- Created
- Sep 6, 2015
- Owner
- 1N3 · User
Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 5 startups in the directory ship primarily in Shell.
Topics
How it got here
What the classifier decided, and when.
Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 97%, self-hostable 69%, hosted offering 64%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.
Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.96. Answered by jev-1.13.0. How the classification works →
Embed your status
Put this badge on your README.
[](https://ossean.com/1N3/Sn1per)
Updates daily, from the last push GitHub saw.
Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.
Related projects