Recommendation : 3. Use environments and tools that limit impacts
Are unused dependencies identified and removed ?
What tool do you use to plot dependencies?
Dependency trees provide the mapping of components and their relationships. The smallest possible dependency tree is efficient because it reduces code volumes, but it does not assume that every branch of that dependency tree is justified by actual use.
Development tools are used to track dependancies never used (CHROME: console / coverage)
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of dependancies used / Number of dependancies
11 other criteria related to the recommendation: Use environments and tools that limit impacts
Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?
Do you use caching mechanisms to limit exchanges ?
Is the data fed back by the APIs really only the data that the application needs when it is requested ?
Is an openSource alternative available for APIs ?
Do the libraries used allow you to take only the components that are actually useful ?
Couldn't the expected functionality be implemented with the native capabilities of the browser ?
Is an openSource alternative available ?
Are all the technical equipment used by the service identified ?
For each equipment, are the characteristics available ?
Are the functionalities related to regulated data processing (health, personal, banking) validated in terms of interoperability ?
Are the latest technical advances used when they really help reduce impact ?