Benchmark(Flutter): Test the extension's ability to find generic and flutter-specific security vulnerabilities in real Flutter apps

Open
  • Is something wrong?
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
flutter
Domain
mobile-dev, security

Research direction

No files, tests, or entry points are named. Start by identifying real Flutter apps and the extension's generic and Flutter-specific security checks, then run the three planned evaluations; done means documenting whether vulnerabilities are found, what Flutter-specific checks apply, and whether performance is strong enough to support community outreach.

Written by the indexing model from the issue text.

Description

Plan

  1. Run our generic security taxonomy against real flutter apps. Do we find the security vulnerabilties?
  2. Investigate to see if there are security checks specific to Flutter, or specifically for app-development code?
  3. Run Flutter-specific checks against real flutter apps. Do we find the security vulnerabilties?

If the performance is strong, we should evangelize the extension to the Flutter community.

Dominant language
TypeScript
Stars
793
Forks
60
No merged PRs in 30d

Getting set up

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.

More from gemini-cli-extensions/security

All issues in gemini-cli-extensions/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.