ossf / ossf/package-analysis

Allow running code as part of dynamic analysis

Open
#672 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dynamic analysis needs discussion
Dominant language
Go
Stars
912
Forks
74
PR merge metrics
No merged PRs in 30d

Description

In Python land for example after we install a wheel (or build and then install from source), allow us to execute some code.

Say we are installing a module called randomcode, then maybe we can also pass a python file like following and interpret/execute accordingly.

import randomcode
randomcode.hello()
randomcode.do_something_which_should_not_do_network_call()

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

No files, tests, or entry points are named. Start by tracing the existing dynamic-analysis workflow after a wheel or source installation, then define how a supplied Python file is executed against the installed module; done means the example can run and observe the package behavior, including the requested no-network-call scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.