opp-repl-speed-tests — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited opp-repl-speed-tests (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Speed tests measure the CPU instruction count of a simulation (via Linux perf counters) and compare it to a baseline in the project's speed_store (default speed.json). Instruction count is more deterministic than wall time, so these tests work on shared/noisy CI machines without flapping.
Upstream reference: https://github.com/omnetpp/opp_repl/blob/main/doc/speed_tests.md
Speed tests require the profile build mode (binary suffix _profile). run_speed_tests() builds it automatically.
update_speed_test_results(simulation_project=inet_project)
run_speed_tests(simulation_project=inet_project)
run_speed_tests(simulation_project=inet_project, working_directory_filter="showcases")
Result codes: PASS / FAIL (plus KEEP/INSERT/UPDATE on updates).
opp_update_speed_test_results --load inet.opp -p inet opp_run_speed_tests --load inet.opp -p inet
results are still correct).
perf_event_paranoid <= 2 on manydistros). macOS cannot run speed tests.
toolchain bump, refresh the baseline before running.
dependent on seed values; hold seeds constant across runs.
opp-repl-profiling — deeper look at where cycles go.opp-repl-running-simulations — underlying run machinery.opp-repl-tasks-and-results — inspect speed-test FAILs.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.