Skip to main content

SQ20133

Detected digital signatures that were made with a certificate before its validity period began.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
failhighmedium2tampering: fail
Reason: signature compliance mistakes

About the issue​

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be self-issued or purchased from certificate authorities. Certificates have a validity period during which they can be used to create signatures. Before the validity period has started, the certificate is considered invalid and should not be used for signing. This issue indicates that a certificate was used before it was intended to create a digital signature. Failing to comply with the established code signing best practices may result in application errors and availability outages.

How to resolve the issue​

  • Check the validity period of the signing certificate and re-sign the software component.

Incidence statistics​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Analysis results are used to calculate incidence statistics for issues (policy violations) that Spectra Assure can detect in software packages.

This section is updated when new data becomes available.

Total amount of packages analyzed

  • Linux: 562K
  • NPM: 5.12M
  • Nuget: 735K
  • PS Gallery: 17K
  • PyPi: 838K
  • RubyGems: 203K
  • VS Code: 113K
  • Windows: 3.7K

Total detections per repository

For every repository, the chart shows the number of packages that triggered the software assurance policy. In other words, it shows how many packages in each package repository were found to have the specific issue described on this page. This information helps you understand how common the issue is across different software communities.

If a repository is absent from the chart, that means none of the packages in that repository triggered this policy during analysis, or the policy was not used during analysis.

Distribution of total detections by project popularity

For every repository, the chart shows how many of the total detections belong to the Top 100 (1-100), Top 1000 (101-1000) and Top 10 000 (1001-10 000) most downloaded projects. This information helps you understand the impact of the issue within each community, making it clearer when the issue affects the most popular projects.

If the chart shows zero values for all of the top project groups, that means all detections were in unranked projects (lower than 10 000 on the list of most downloaded projects).