---
tags: wp2.4, wp2, deliverable
title: Ideas and things to remember for D2.4
---

# Privacy and security labels

## Library Label
Add a new JSON schema containing an array of API Labels.
Objects compliant to this schema are used in input by the tool developed by Michele (currently called [Manifest](https://github.com/sifis-home/manifest)) that creates the App Label.
The array contains *all* the API Labels extracted from [sifis-api](https://github.com/sifis-home/sifis-api).
This schema could include a field `version`.

{
    version: 0.1,
    API Label array: [
                        {api-label1}, 
                        {api-label2}, 
                        ...
    ]
}

> Let's think if we need a schema for this...

# Code errors through static analysis

(need to evaluate this part, we can advise that through an example, that could be helpful for a developer)

One property consists of **finding** and **counting** each code syntax and logic error without the need to build an entire software, *only* through the analysis of the *Abstract Syntax Tree* nodes obtained parsing the programming language grammar. In this way, the write-check-code cycle results more lightweight and faster because it is not necessary to run all code compilation or interpretation optimizations. In addition, these checks provide a guarantee that the build process is *correct*.

# Code benchmarking

(hyperfine tool)

*Code benchmarking* assesses the relative performance of a program by running a number of standard tests and trials against it.

- Explain the most common benchmarking systems that a developer could use to benchmark a code.