Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Issues
  • #710
Closed
Open
Issue created May 04, 2016 by Administrator@rootContributor

More scan metrics

Created by: dnyrop

Hi

When scanning a target a big part of the success depends on Arachni being able to reach the target and get a valid response back.

That doesn't always happen (to no fault of Arachni), which makes the scan results vary from one scan to another.

It would be very helpful to be able to assess the validity of a scan, with two metrics in the scan report:

  1. The number of successful checks
  2. The number of failed (including timed out) checks

This would make it possible to assess the validity of a scan and run new one in case of too many failed checks.

Assignee
Assign to
Time tracking