Use case

A browser extensionwith small reach.

An extension is a few files with wide access to the browser. Adams helps keep its permissions and keys honest.

Lite and Pro
// the problem

What goes wrong

Permissions only growIt is easy to ask for access to every site because it makes the first version work. Reviewers and users notice.
Keys ship inside the packageAnything in an extension can be read by whoever installs it. A secret placed there is not a secret.
// what adams does

What Adams does

Catches a key before packagingLite: keys and tokens in the source are blocked at commit, so they do not ship in the zip.
Reviews the change separatelyPro: a reviewer asks whether each permission is needed.
Scopes a security checkPro: check input handling for content that comes from pages you do not control.
// worked example

An example

A permission review

Illustrative session.

~/project~/your-project · example
/adams:review
P1: access to all sites, one site is used
P1: page text is inserted as html
Fix these findings? Yes (recommended)
✓ Fixed and looked at again
// faq

Questions

Will Adams pass store review for me?

No. It catches common problems early. Stores have their own rules.

Does it know every browser?

It reads your code. Check each browser store documentation for its rules.

What is free?

The secret and git guards.

// related

Keep reading