The dataset contains recordings of developers interacting with the QualityAssistant static analysis plugin in Pharo IDE (version 5 and 6). We recorded 7786 development sessions from 547 developers in a time span of 322 days. In a regular programming session, the developer launches the Pharo IDE and uses the code editor to display code. The Pharo IDE allows the developer to work on a single method or class definition at a time. QualityAssistant then evaluates the browsed code; if the tool finds quality violations, it displays them in the code editor. The developer eventually edits the code, i.e., performing code transformations either manually or using automated tools. After the developer compiles the code, QualityAssistant re-evaluates it and thus more or fewer violations may be displayed to the developer. By instrumenting this tool, we were able to collect the data about violation reports seen by Pharo developers. More than 933 thousand events corresponding to violations shown in the IDE were collected.