chore: update archived packages (#97)

FLAGS.md

@@ -96,7 +96,7 @@ Example: ISC OR GPL-2.0-with-GCC-exception.
 
 
 
-Under the hood we use [@nodesecure/licenses-conformance](https://github.com/NodeSecure/licenses-conformance) to assert licenses conformance!
+Under the hood we use [`@nodesecure/conformance`](https://github.com/NodeSecure/scanner/tree/master/workspaces/conformance) to assert licenses conformance!
 
 </details><details><summary>🐲 hasNativeCode</summary>
 
@@ -116,7 +116,7 @@ This flag mean that we have not detected any licenses in the npm Tarball (or som
 
 
 
-The code and logic behind the detection is handled in the [npm-tarball-license-parser](https://github.com/fraxken/npm-tarball-license-parser) package.
+The code and logic behind the detection is handled in the [`@nodesecure/tarball`](https://github.com/NodeSecure/scanner/tree/master/workspaces/tarball) package.
 
 
 
@@ -146,7 +146,7 @@ We currently working to implement NVD and [OSV](https://osv.dev/).
 
 </details><details><summary>⚠ hasWarnings</summary>
 
-This means that the [SAST](https://www.gartner.com/en/information-technology/glossary/static-application-security-testing-sast) Scanner has detected several problems by analyzing the **Abstract Syntax Tree (AST)** of a JavaScript source code. All warnings are accurately documented [here](https://github.com/fraxken/js-x-ray#warnings-legends-v20).
+This means that the [SAST](https://www.gartner.com/en/information-technology/glossary/static-application-security-testing-sast) Scanner has detected several problems by analyzing the **Abstract Syntax Tree (AST)** of a JavaScript source code. All warnings are accurately documented [here](https://github.com/NodeSecure/js-x-ray#legends).
 
 </details><details><summary>💀 isDead</summary>
 
@@ -195,4 +195,4 @@ This can happen, for example, when the package uses **tags** such as:
 *   @beta
 *   @next
 
-</details>
+</details>

src/flags/hasMultipleLicenses.html

@@ -14,6 +14,6 @@ <h1>📚 hasMultipleLicenses</h1>
     <p>Example: <span>ISC OR GPL-2.0-with-GCC-exception</span>.</p>
     <br />
     <p>
-        Under the hood we use <a href="https://github.com/NodeSecure/licenses-conformance">@nodesecure/licenses-conformance</a> to assert licenses conformance!
+        Under the hood we use <a href="https://github.com/NodeSecure/scanner/tree/master/workspaces/conformance">@nodesecure/conformance</a> to assert licenses conformance!
     </p>
 </div>

src/flags/hasNoLicense.html

@@ -7,7 +7,7 @@ <h1>📜 hasNoLicense</h1>
     </p>
     <br />
     <p>
-        The code and logic behind the detection is handled in the <a href="https://github.com/fraxken/npm-tarball-license-parser">npm-tarball-license-parser</a> package.
+        The code and logic behind the detection is handled in the <a href="https://github.com/NodeSecure/scanner/tree/master/workspaces/tarball">@nodesecure/tarball</a> package.
     </p>
     <br />
     <p>

src/flags/hasWarnings.html

@@ -3,6 +3,6 @@ <h1>⚠ hasWarnings</h1>
     <p>
         This means that the <a href="https://www.gartner.com/en/information-technology/glossary/static-application-security-testing-sast" target="_blank">SAST</a> Scanner
         has detected several problems by analyzing the <b>Abstract Syntax Tree (AST)</b> of a JavaScript source code.
-        All warnings are accurately documented <a href="https://github.com/fraxken/js-x-ray#warnings-legends-v20" target="_blank">here</a>.
-    </p> 
+        All warnings are accurately documented <a href="https://github.com/NodeSecure/js-x-ray#legends" target="_blank">here</a>.
+    </p>
 </div>