How up to date is your software?

Modern software is largely built from ready-made components by other developers, called packages. If they are not updated, security fixes are missing and every later update gets bigger and more expensive. This check shows how far behind the packages of your PHP and JavaScript projects are. You need neither access to the code nor IT knowledge: two files per project are enough.

How it works

  1. Get the filesTwo small files per project from its code. Below you can see where to find them or how to ask your team for them.
  2. UploadUp to five projects at once. The files are only used for the analysis and deleted right afterwards.
  3. Understand the resultYou get a plain-language assessment with a recommendation, plus the details for your development team.

Upload files

Which files do you need?

Two files per project from the main folder of its code. Which ones depends on the programming language:

  • PHP

    e.g. Laravel, Symfony, Shopware, TYPO3, Magento

    composer.json and composer.lock

  • JavaScript

    e.g. React, Vue, Angular, Next.js, Node.js

    package.json and package-lock.json, npm-shrinkwrap.json, or yarn.lock

Many web projects use both. Then upload all the files you find; the tool matches them to their projects automatically. Not sure which language your project uses? Just check which of these files exist.

The files contain none of your application's code, only the list of packages it uses and their versions.

Where do I find the files?

Ask your development team or agency

This is usually the easiest way. Copy this message and send it to whoever looks after your software:

Hi, For a check of our software dependencies I need these files from the main folder of our project, where they exist: - PHP: composer.json and composer.lock - JavaScript: package.json and package-lock.json, npm-shrinkwrap.json, or yarn.lock No source code is needed, just these files. If we have several projects, please send the files for each one. Thank you!

In the code repository (GitHub, GitLab, Bitbucket)
  1. Open the project in your browser. The files are right in the file list on the project's start page, not in a subfolder.
  2. Click one of the files, e.g. composer.json.
  3. Download it with the download icon (called “Download raw file” on GitHub and “Download” on GitLab). If there is none, ask your team as described above.
  4. Repeat this for the second file.
On your computer
  1. Open the folder that contains the project's code.
  2. The files are directly in this folder, usually next to subfolders like src, vendor or node_modules.
  3. Do not take the files of the same name from vendor or node_modules: they belong to the individual packages, not to your project.

Windows often hides file extensions. composer.lock then shows as “composer” with the type “LOCK File”, composer.json as “composer” with the type “JSON File”.

Can't find the files?

In a free 15-minute consultation we help you find the files and put the result into context.

Both files are needed: one lists the packages, the other (the lockfile) records exactly which versions are installed.

Tip: select several files at once by holding Ctrl (Windows) or Cmd (Mac).

You can upload the files of several projects at once: they are matched to their projects by their content.

Files are only used for the analysis and deleted right afterwards. Privacy policy (opens in a new tab)

0 of 5 projects

Not ready yet:

  • Add at least one project: a manifest and its lockfile.