|
Atelier Lumen
Security of your application: Boulangerie Martin, boutique-en-lignePrepared for Claire Martin. Version of 01/11/2026: 142 packages analysed. The project's code was analysed too.
2 updates planned
No known vulnerability is being exploited right now against the components of your application. 2 components have a known vulnerability to handle: we are updating them by 15/11/2026. The code contains a secret key to remove and replace. 2updates to do
1package to check
31known vulnerabilities, 28 of them dismissed
4serious problems in the code
What we are fixing
What we are checking
Vulnerability handling registerDeadlines from detection: 7 days for an actively exploited or critical vulnerability, 30 days for high severity, 90 days for medium severity, 180 days for low severity.
What was checkedComponents142 packages checked against the OSV and FIRST EPSS databases and the CISA KEV catalogue.
Made-up or malicious packagesOne package not found in its registry, often made up by an AI.
Keys and passwordsOne secret key in the code: to remove and replace.
Application code3 serious problems to fix (data access, injection or configuration).
A vulnerability is dismissed when it does not affect your application: part of the component not used, very low risk in practice, or a decision checked by our team. The list of the 28 dismissed vulnerabilities, with the reason for each, is available on request from Atelier Lumen. This report does not replace a security audit. Sources: OSV, FIRST EPSS, CISA KEV (catalogue of makiety), PyPI, npm.
Atelier Lumen
Analysis made with Tamiso
|
How it works
Under your brand
Your agency's name, logo and contact. Your client opens the report through a link, without an account, or you save it as a PDF.
Your fix dates
For each update, the planned date and, if needed, an explanation. Dismissed vulnerabilities are counted; their list stays with you.
The fix register
Detection date, fix date and deadline by severity: what clients subject to NIS2 ask for.