mProjectsCode / mProjectsCode/glass-lint

Add generalized flow matchers for modeling e.g. `fetch -> eval` flow

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

The current object flow matchers are nice for certain things like DOM tags, but they can't express more general data flows that pass e.g. strings.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing object flow matchers, which the issue identifies as the relevant starting point. Determine how they currently model flows such as DOM tags and what generalized representation is needed for string flows like fetch -> eval. Done should provide a defined way to express and match these generalized data flows.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.