bytecode-viewer

Konloch/bytecode-viewer

A Java 8+ Jar & Android APK Reverse Engineering Suite (Decompiler, Editor, Debugger & More)

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Jul 17, 2026
77 days ago
Ship score
29/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 15,600 → 15,655 (Aug 18 – Sep 29, 2026)
+34 stars in the 28 days to 2026-09-29

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
15.7K
Forks
1.3K
Open issues
103
Watchers
370
Primary language
Java
Created
Oct 14, 2014
Owner
Konloch · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 35 startups in the directory ship primarily in Java.

Topics

#android#apk#baksmali#bytecode#bytecode-viewer#cfr#compiler#decompiler#dex2jar#fernflower#hacktoberfest#java#java-decompiler#jsp#krakatau#procyon#recompiler#smali#static-analysis#war

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 32% (self-hostable 39%, hosted offering 22%). 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. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 2026-07-17This is the badge for Konloch/bytecode-viewer, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/Konloch/bytecode-viewer.svg)](https://ossean.com/Konloch/bytecode-viewer)

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.