Open-source project
jlevy/og-equity-compensation avatar
jlevy/og-equity-compensation

The Open Guide to Equity Compensation: A Repository That Points Elsewhere

Stock options, RSUs, taxes — read the latest edition: www.holloway.com/ec

11,512 stars530 forksUnknownLicense varies

At a glance

What is it?
jlevy/og-equity-compensation is now a pointer repository: the guide lives on Holloway, and the GitHub tree holds a README, a contributing guide and images. This is what the repository actually contains, what it covers, and where it stops.
Who is it for?
Adopt this repository as a signpost, not as a working codebase: read the README, then follow its link to the Holloway edition if you want search, bookmarks, expert commentary and PDF or EPUB download. Do not clone it expecting tooling, a calculator or a data set, because the top level holds only CONTRIBUTING.md, README.md and images/.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 166 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • jlevy/og-equity-compensation11,512 ★ · +12
Star history
Repository2026-09-222026-11-15
jlevy/og-equity-compensation11.5k11.5k

12 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What the README says this repository is now

The first line of the README is a notice, not an introduction: the guide is now published on Holloway, and readers are sent there for search, bookmarks and highlights, expert commentary, and PDF or EPUB download. That single sentence reframes the whole repository. If you arrived from a search engine expecting the text of the guide in Markdown, the README tells you the canonical copy sits elsewhere.

The top level of the repository supports that reading. It contains CONTRIBUTING.md, README.md and an images/ directory. There is no source tree, no build file, no schema and no test suite in the entries listed. So the useful question is not how the code works, because there is no code to work through, but what the remaining files are for and whether the GitHub copy is still the right place to read.

The README keeps its original framing even though the hosting moved. It describes equity compensation as the practice of granting partial ownership in a company in exchange for work, and calls the ways equity can be granted, including restricted stock, stock options and restricted stock units, notoriously complex. That tone is the point: the repository is the public face of a long-form reference, and the README is the doorway.

Who the guide is written for, and the scope limits it states itself

The README names its audiences directly: employees, candidates for a job, hiring managers, founders and students. It lists the situations that bring people in, including hearing terms like strike price, ISOs, RSUs, 83(b) election, 409A valuation, AMT and early exercise without knowing which apply; weighing the equity component of an offer; joining a startup for the first time and facing the paperwork; leaving a company while holding stock or options; and working through an acquisition, an IPO or a shutdown.

The scope section is the most useful part of the README for anyone deciding whether to trust the guide. It states that the guide currently covers equity compensation in C corporations in the United States, for most employees, advisors and independent contractors in private companies, from startups through larger private corporations, with limited coverage of public companies. It then lists what is not yet covered: ESPPs in public companies, full details on executive equity compensation, compensation outside the United States, and compensation in companies other than C corporations, including LLCs and S corporations.

That is an unusually honest boundary, and it matters more than the marketing language around it. A reader in a UK limited company, or an executive negotiating a package built around performance awards, is told plainly that this reference is not aimed at them and is pointed to other resources and professional advice. Treat the scope list as the first filter before you spend an evening reading.

Installing nothing: how to get the guide and start reading

There is no installation step for this repository. The README gives no package, no build command and no runtime, because the repository's job is to point at the published edition. The practical setup is therefore about getting a readable copy rather than running anything.

The README's own instruction is to read the guide on Holloway, where it says search, bookmarks and highlights, expert commentary, and PDF or EPUB download are available. In a shell, that means opening the published edition in a browser rather than cloning the repository:

bash
open https://www.holloway.com/g/equity-compensation/about

If you want the repository itself, for the README text and the images, a clone is enough. Nothing needs to be installed afterwards:

bash
git clone https://github.com/jlevy/og-equity-compensation.git
cd og-equity-compensation
ls

You should see CONTRIBUTING.md, README.md and images/ listed. That is the whole tree at the top level, and it is the clearest signal that this is a pointer repository rather than an application.

A sensible first read is the README's scope section, followed by the sections it cross-links. The README describes the guide as at least a three-hour read with links to three hundred sources, so plan for a session rather than a skim. If you only care about one decision, such as whether to exercise options before leaving a job, start from the relevant chapter on Holloway and use its search, which the GitHub copy does not provide.

The maintenance question: what the repository timeline actually shows

The repository is not archived, and the last push was on 2026-06-02. That is a real signal but a narrow one. A push can be a README edit, an image change or a contribution note, and the visible top level gives no changelog or release history to interpret it against. The repository has no published GitHub releases, so there is no versioned artifact to compare across time.

The README itself explains why the repository's activity is a weak proxy for the guide's currency. It says the guide does not purport to be either perfect or complete, that a reference like this is always in process, and that Holloway is testing features to let the community suggest improvements, contribute new sections and call out anything that needs revision. In other words, the project's own description places editorial work on the Holloway platform, not in this Git tree.

For a reader, that changes what to check. The useful question is not whether this repository saw a commit this year, but whether the edition you are reading is the current one. The README sends you to Holloway for the published text; a fork or a cached copy of the Markdown will not tell you when it was last revised. The upgrade cost is therefore near zero in tooling terms and non-trivial in attention terms: you re-read the current edition rather than pulling a tag.

Licence and reuse: what the repository does not settle

The repository metadata carries no licence identifier. CONTRIBUTING.md exists, which suggests contributions are expected and governed by some process.

That gap matters because the guide is a long-form reference with many contributors, and the README says the authors welcome and will credit help. If you plan to mirror the guide, translate it, or reuse the images in training material, check the licensing terms first.

This is not legal advice, and it should not be read as one. The concrete step is to look for the licence file or terms on the Holloway edition and to read CONTRIBUTING.md before reusing anything. Treat the absence of a licence identifier in the repository metadata as a reason to ask rather than a permission.

Where the guide stops and professional advice begins

The README is explicit that the topic is best understood by tax attorneys, corporate lawyers and other professionals, and that decisions about negotiating an offer and exercising stock options can have major financial consequences. It also warns that equity may be illiquid for a long time or ultimately worth nothing, while taxes and exercise costs may not be recouped, and that employees can hit catastrophic tax pitfalls by not anticipating the consequences of their choices.

That is the strongest limitation in the README, and it is a limitation of the genre rather than of the writing. A reference can explain the mechanics of an 83(b) election, the difference between an ISO and an NSO, or how the AMT trap works, but it cannot know your grant documents, your jurisdiction, your tax position or your company's 409A valuation. The README frames the guide as preparation for a conversation with a professional, not a replacement for one.

How it differs from a calculator or a benchmark survey

People searching around this topic often want a number: what a given percentage is worth, or how a grant compares with the market. This project does not do that. There is no calculator, no data set and no benchmark table in the repository entries, and the README describes the guide as a consolidated reference that is practical, thoughtful and concise, with concrete suggestions and pitfalls to avoid. The output is understanding, not a figure.

A calculator takes your inputs, such as strike price, share count, current valuation and tax rate, and returns an outcome. A benchmark survey takes a sample of companies and returns a distribution. The Open Guide takes none of your inputs. It is a consolidated reference that explains terminology and flags tax pitfalls. The difference in approach is the difference between a formula and a briefing.

That is also why the guide's stated scope is narrow by design. A calculator can be jurisdiction-agnostic because it is arithmetic; a reference cannot, which is why the README limits itself to C corporations in the United States and points everyone else to other resources. If you need a number, you will need a calculator or a professional. If you need to understand what the number means before you act on it, this is the resource the README is advertising.

Editorial conclusion

Adopt this repository as a signpost, not as a working codebase: read the README, then follow its link to the Holloway edition if you want search, bookmarks, expert commentary and PDF or EPUB download. Do not clone it expecting tooling, a calculator or a data set, because the top level holds only CONTRIBUTING.md, README.md and images/. Before relying on any chapter, check the README's own scope list, which limits the guide to C corporations in the United States and says compensation outside the United States is not yet covered, and confirm the current edition on Holloway rather than trusting a stale fork of the text.

Frequently asked questions

What does equity compensation mean in the Open Guide to Equity Compensation?

The README defines equity compensation as the practice of granting partial ownership in a company in exchange for work, and says that in its ideal form it aligns the interests of individual employees with the goals of the company. The guide covers the ways equity can be granted, including restricted stock, stock options and restricted stock units.

What are the three types of equity compensation the guide covers?

The README names restricted stock, stock options and restricted stock units as the ways equity can be granted as compensation, and describes them as notoriously complex. It also notes that the guide covers equity compensation for most employees, advisors and independent contractors in private C corporations in the United States.

Is 1% equity in a startup good according to the Open Guide to Equity Compensation?

The README's introduction warns that equity may be illiquid for a long time or ultimately worth nothing, that taxes and exercise costs may not be recouped, and that the guide's purpose is to help readers understand the details well enough to make their own decisions and to talk to professionals.

Official sources

  1. Issues
  2. jlevy/og-equity-compensation on GitHub
  3. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/jlevy-og-equity-compensation.svg)](https://hysenlabs.com/projects/jlevy-og-equity-compensation)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/jlevy-og-equity-compensation.svg)](https://hysenlabs.com/projects/jlevy-og-equity-compensation)

Was this useful?