The following new code scanning alerts showed up recently:

- https://github.com/mozilla/pdf.js/security/code-scanning/402
- https://github.com/mozilla/pdf.js/security/code-scanning/401
- https://github.com/mozilla/pdf.js/security/code-scanning/400
- https://github.com/mozilla/pdf.js/security/code-scanning/399
- https://github.com/mozilla/pdf.js/security/code-scanning/398

There is a note in there that this is debugging code code, and it's indeed not called from anywhere. It has also mostly been changed 12 years ago.

@Snuffleupagus What do you think? Should we get rid of it, or is this something you have used or think is useful to keep? In the latter case we can just silence the alert.
/* Copyright 2012 Mozilla Foundation
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
/* globals CFFDictDataMap, CFFDictPrivateDataMap, CFFEncodingMap, CFFStrings,
           Components, Dict, dump, FormatError, netscape, Stream */
'use strict';
/*
 * The Type2 reader code below is only used for debugging purpose since Type2
 * is only a CharString format and is never used directly as a Font file.
 *
 * So the code here is useful for dumping the data content of a .cff file in
 * order to investigate the similarity between a Type1 CharString and a Type2
 * CharString or to understand the structure of the CFF format.
 */
/*
 * Build a charset by assigning the glyph name and the human readable form
 * of the glyph data.
 */
function readCharset(aStream, aCharstrings) {