Executive summary
NaturalNode/natural is rated At risk because critical security findings are open. Its score is held back because we found no recorded design decisions and no architecture document or diagram. It scores 59 out of 100, which the At risk rating leaves unchanged.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Having someone learn and document the six files no active contributor knows comes next, worth about 2 points. Raising Maturity to 70 would lift the score to about 66.
Sixteen known security holes in the packages the code depends on can be used by attackers. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The test that checks nothing needs to check the result it produces.
The product code is 18,399 lines, about €28,000 to rebuild.
If Maturity rose from 50 to 70, the lowest score rated Strong, the score would rise from 59 to about 66.
New since the last survey: 12 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Cyclomatic Complexity · Complex function stem (cyclomatic 12, cognitive 19) REDACTED
- Cyclomatic Complexity · Complex function handleJ (cyclomatic 12, cognitive 15) lib/natural/phonetics/double_metaphone.js
- Cyclomatic Complexity · Complex function ngrams (cyclomatic 11, cognitive 14) lib/natural/ngrams/ngrams_zh.js
- Cyclomatic Complexity · Complex function trainParallelBatches (cyclomatic 11, cognitive 12) lib/natural/classifiers/classifier_train_parallel.js
- Dependency Hygiene · Unused dependency 'source-map-support'
- Dependency Hygiene · Unused dependency 'sylvester'
Fixed since the last survey: 12 findings
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block (8 lines × 6 locations) lib/natural/stemmers/stemmer_fa.js
- Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) lib/natural/stemmers/token.js
- Code Duplication · Duplicated block (7 lines × 2 locations) lib/natural/classifiers/maxent/Classifier.js
- Code Duplication · Duplicated block (7 lines × 2 locations) lib/natural/ngrams/ngrams_zh.js
- Code Duplication · Duplicated block (6 lines × 2 locations) lib/natural/normalizers/normalizer_no.js
- Code Duplication · Duplicated block (6 lines × 3 locations) lib/natural/stemmers/porter_stemmer_fr.js
- Code Duplication · Duplicated block (5 lines × 2 locations) lib/natural/stemmers/porter_stemmer_es.js
Rebuild cost: about €28,000 · Estimate
| Cost to rebuild | €9,400 to €47,000, for 157 to 498 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 18,399 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 lib | 2 lib.natural.brill_pos_tagger.lib.Corpus | 3 lib.natural.brill_pos_tagger.lib.Sentence | 4 lib.natural.classifiers.classifier | 5 lib.natural.classifiers.maxent.Element | 6 lib.natural.phonetics.phonetic | 7 lib.natural.stemmers.stemmer_de | 8 lib.natural.tokenizers.tokenizer | 9 lib.natural.classifiers.bayes_classifier | 10 lib.natural.classifiers.logistic_regression_classifier | 11 lib.natural.classifiers.maxent.POS.ME_Corpus | 12 lib.natural.classifiers.maxent.POS.ME_Sentence | 13 lib.natural.classifiers.maxent.POS.POS_Element | 14 lib.natural.classifiers.maxent.SimpleExample.SE_Element | 15 lib.natural.phonetics.dm_soundex | 16 lib.natural.phonetics.double_metaphone | 17 lib.natural.phonetics.metaphone | 18 lib.natural.phonetics.soundex | 19 lib.natural.stemmers.porter_stemmer_es | 20 lib.natural.stemmers.porter_stemmer_nl | 21 lib.natural.tokenizers.aggressive_tokenizer | 22 lib.natural.tokenizers.aggressive_tokenizer_de | 23 lib.natural.tokenizers.aggressive_tokenizer_es | 24 lib.natural.tokenizers.aggressive_tokenizer_fa | 25 lib.natural.tokenizers.aggressive_tokenizer_fr | 26 lib.natural.tokenizers.aggressive_tokenizer_hi | 27 lib.natural.tokenizers.aggressive_tokenizer_id | 28 lib.natural.tokenizers.aggressive_tokenizer_it | 29 lib.natural.tokenizers.aggressive_tokenizer_nl | 30 lib.natural.tokenizers.aggressive_tokenizer_no | 31 lib.natural.tokenizers.aggressive_tokenizer_pl | 32 lib.natural.tokenizers.aggressive_tokenizer_pt | 33 lib.natural.tokenizers.aggressive_tokenizer_ru | 34 lib.natural.tokenizers.aggressive_tokenizer_sv | 35 lib.natural.tokenizers.aggressive_tokenizer_uk | 36 lib.natural.tokenizers.aggressive_tokenizer_vi | 37 lib.natural.tokenizers.regexp_tokenizer | 38 lib.natural.tokenizers.sentence_tokenizer | 39 lib.natural.tokenizers.sentence_tokenizer_deprecated | 40 lib.natural.tokenizers.tokenizer_case |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 lib | ||||||||||||||||||||||||||||||||||||||||
| 2 lib.natural.brill_pos_tagger.lib.Corpus | ||||||||||||||||||||||||||||||||||||||||
| 3 lib.natural.brill_pos_tagger.lib.Sentence | ||||||||||||||||||||||||||||||||||||||||
| 4 lib.natural.classifiers.classifier | ||||||||||||||||||||||||||||||||||||||||
| 5 lib.natural.classifiers.maxent.Element | ||||||||||||||||||||||||||||||||||||||||
| 6 lib.natural.phonetics.phonetic | ||||||||||||||||||||||||||||||||||||||||
| 7 lib.natural.stemmers.stemmer_de | ||||||||||||||||||||||||||||||||||||||||
| 8 lib.natural.tokenizers.tokenizer | ||||||||||||||||||||||||||||||||||||||||
| 9 lib.natural.classifiers.bayes_classifier | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 lib.natural.classifiers.logistic_regression_classifier | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 lib.natural.classifiers.maxent.POS.ME_Corpus | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 lib.natural.classifiers.maxent.POS.ME_Sentence | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 lib.natural.classifiers.maxent.POS.POS_Element | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 lib.natural.classifiers.maxent.SimpleExample.SE_Element | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 lib.natural.phonetics.dm_soundex | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 lib.natural.phonetics.double_metaphone | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 lib.natural.phonetics.metaphone | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 lib.natural.phonetics.soundex | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 lib.natural.stemmers.porter_stemmer_es | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 lib.natural.stemmers.porter_stemmer_nl | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 lib.natural.tokenizers.aggressive_tokenizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 lib.natural.tokenizers.aggressive_tokenizer_de | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 lib.natural.tokenizers.aggressive_tokenizer_es | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 lib.natural.tokenizers.aggressive_tokenizer_fa | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 lib.natural.tokenizers.aggressive_tokenizer_fr | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 lib.natural.tokenizers.aggressive_tokenizer_hi | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 lib.natural.tokenizers.aggressive_tokenizer_id | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 lib.natural.tokenizers.aggressive_tokenizer_it | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 lib.natural.tokenizers.aggressive_tokenizer_nl | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 lib.natural.tokenizers.aggressive_tokenizer_no | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 lib.natural.tokenizers.aggressive_tokenizer_pl | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 lib.natural.tokenizers.aggressive_tokenizer_pt | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 lib.natural.tokenizers.aggressive_tokenizer_ru | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 lib.natural.tokenizers.aggressive_tokenizer_sv | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 lib.natural.tokenizers.aggressive_tokenizer_uk | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 lib.natural.tokenizers.aggressive_tokenizer_vi | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 lib.natural.tokenizers.regexp_tokenizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 lib.natural.tokenizers.sentence_tokenizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 lib.natural.tokenizers.sentence_tokenizer_deprecated | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 lib.natural.tokenizers.tokenizer_case | 1 |
9→4 lib.natural.classifiers.bayes_classifier uses lib.natural.classifiers.classifier✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.bayes_classifier uses a type in lib.natural.classifiers.classifier.
- The types involved
lib.natural.classifiers.bayes_classifier.BayesClassifier→lib.natural.classifiers.classifier.Classifier
- Direction
- lib.natural.classifiers.bayes_classifier uses lib.natural.classifiers.classifier, so a change to lib.natural.classifiers.classifier can break lib.natural.classifiers.bayes_classifier, while a change to lib.natural.classifiers.bayes_classifier can't break lib.natural.classifiers.classifier.
- Position
- Below the diagonal: lib.natural.classifiers.bayes_classifier uses a module listed above it, which is the healthy direction.
10→4 lib.natural.classifiers.logistic_regression_classifier uses lib.natural.classifiers.classifier✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.logistic_regression_classifier uses a type in lib.natural.classifiers.classifier.
- The types involved
lib.natural.classifiers.logistic_regression_classifier.LogisticRegressionClassifier→lib.natural.classifiers.classifier.Classifier
- Direction
- lib.natural.classifiers.logistic_regression_classifier uses lib.natural.classifiers.classifier, so a change to lib.natural.classifiers.classifier can break lib.natural.classifiers.logistic_regression_classifier, while a change to lib.natural.classifiers.logistic_regression_classifier can't break lib.natural.classifiers.classifier.
- Position
- Below the diagonal: lib.natural.classifiers.logistic_regression_classifier uses a module listed above it, which is the healthy direction.
11→2 lib.natural.classifiers.maxent.POS.ME_Corpus uses lib.natural.brill_pos_tagger.lib.Corpus✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.maxent.POS.ME_Corpus uses a type in lib.natural.brill_pos_tagger.lib.Corpus.
- The types involved
lib.natural.classifiers.maxent.POS.ME_Corpus.MECorpus→lib.natural.brill_pos_tagger.lib.Corpus.Corpus
- Direction
- lib.natural.classifiers.maxent.POS.ME_Corpus uses lib.natural.brill_pos_tagger.lib.Corpus, so a change to lib.natural.brill_pos_tagger.lib.Corpus can break lib.natural.classifiers.maxent.POS.ME_Corpus, while a change to lib.natural.classifiers.maxent.POS.ME_Corpus can't break lib.natural.brill_pos_tagger.lib.Corpus.
- Position
- Below the diagonal: lib.natural.classifiers.maxent.POS.ME_Corpus uses a module listed above it, which is the healthy direction.
12→3 lib.natural.classifiers.maxent.POS.ME_Sentence uses lib.natural.brill_pos_tagger.lib.Sentence✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.maxent.POS.ME_Sentence uses a type in lib.natural.brill_pos_tagger.lib.Sentence.
- The types involved
lib.natural.classifiers.maxent.POS.ME_Sentence.MESentence→lib.natural.brill_pos_tagger.lib.Sentence.Sentence
- Direction
- lib.natural.classifiers.maxent.POS.ME_Sentence uses lib.natural.brill_pos_tagger.lib.Sentence, so a change to lib.natural.brill_pos_tagger.lib.Sentence can break lib.natural.classifiers.maxent.POS.ME_Sentence, while a change to lib.natural.classifiers.maxent.POS.ME_Sentence can't break lib.natural.brill_pos_tagger.lib.Sentence.
- Position
- Below the diagonal: lib.natural.classifiers.maxent.POS.ME_Sentence uses a module listed above it, which is the healthy direction.
13→5 lib.natural.classifiers.maxent.POS.POS_Element uses lib.natural.classifiers.maxent.Element✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.maxent.POS.POS_Element uses a type in lib.natural.classifiers.maxent.Element.
- The types involved
lib.natural.classifiers.maxent.POS.POS_Element.POSElement→lib.natural.classifiers.maxent.Element.Element
- Direction
- lib.natural.classifiers.maxent.POS.POS_Element uses lib.natural.classifiers.maxent.Element, so a change to lib.natural.classifiers.maxent.Element can break lib.natural.classifiers.maxent.POS.POS_Element, while a change to lib.natural.classifiers.maxent.POS.POS_Element can't break lib.natural.classifiers.maxent.Element.
- Position
- Below the diagonal: lib.natural.classifiers.maxent.POS.POS_Element uses a module listed above it, which is the healthy direction.
14→5 lib.natural.classifiers.maxent.SimpleExample.SE_Element uses lib.natural.classifiers.maxent.Element✕
- Connections
- 1 pair of types, where a type in lib.natural.classifiers.maxent.SimpleExample.SE_Element uses a type in lib.natural.classifiers.maxent.Element.
- The types involved
lib.natural.classifiers.maxent.SimpleExample.SE_Element.SEElement→lib.natural.classifiers.maxent.Element.Element
- Direction
- lib.natural.classifiers.maxent.SimpleExample.SE_Element uses lib.natural.classifiers.maxent.Element, so a change to lib.natural.classifiers.maxent.Element can break lib.natural.classifiers.maxent.SimpleExample.SE_Element, while a change to lib.natural.classifiers.maxent.SimpleExample.SE_Element can't break lib.natural.classifiers.maxent.Element.
- Position
- Below the diagonal: lib.natural.classifiers.maxent.SimpleExample.SE_Element uses a module listed above it, which is the healthy direction.
15→6 lib.natural.phonetics.dm_soundex uses lib.natural.phonetics.phonetic✕
- Connections
- 1 pair of types, where a type in lib.natural.phonetics.dm_soundex uses a type in lib.natural.phonetics.phonetic.
- The types involved
lib.natural.phonetics.dm_soundex.SoundExDM→lib.natural.phonetics.phonetic.Phonetic
- Direction
- lib.natural.phonetics.dm_soundex uses lib.natural.phonetics.phonetic, so a change to lib.natural.phonetics.phonetic can break lib.natural.phonetics.dm_soundex, while a change to lib.natural.phonetics.dm_soundex can't break lib.natural.phonetics.phonetic.
- Position
- Below the diagonal: lib.natural.phonetics.dm_soundex uses a module listed above it, which is the healthy direction.
16→6 lib.natural.phonetics.double_metaphone uses lib.natural.phonetics.phonetic✕
- Connections
- 1 pair of types, where a type in lib.natural.phonetics.double_metaphone uses a type in lib.natural.phonetics.phonetic.
- The types involved
lib.natural.phonetics.double_metaphone.DoubleMetaphone→lib.natural.phonetics.phonetic.Phonetic
- Direction
- lib.natural.phonetics.double_metaphone uses lib.natural.phonetics.phonetic, so a change to lib.natural.phonetics.phonetic can break lib.natural.phonetics.double_metaphone, while a change to lib.natural.phonetics.double_metaphone can't break lib.natural.phonetics.phonetic.
- Position
- Below the diagonal: lib.natural.phonetics.double_metaphone uses a module listed above it, which is the healthy direction.
17→6 lib.natural.phonetics.metaphone uses lib.natural.phonetics.phonetic✕
- Connections
- 1 pair of types, where a type in lib.natural.phonetics.metaphone uses a type in lib.natural.phonetics.phonetic.
- The types involved
lib.natural.phonetics.metaphone.Metaphone→lib.natural.phonetics.phonetic.Phonetic
- Direction
- lib.natural.phonetics.metaphone uses lib.natural.phonetics.phonetic, so a change to lib.natural.phonetics.phonetic can break lib.natural.phonetics.metaphone, while a change to lib.natural.phonetics.metaphone can't break lib.natural.phonetics.phonetic.
- Position
- Below the diagonal: lib.natural.phonetics.metaphone uses a module listed above it, which is the healthy direction.
18→6 lib.natural.phonetics.soundex uses lib.natural.phonetics.phonetic✕
- Connections
- 1 pair of types, where a type in lib.natural.phonetics.soundex uses a type in lib.natural.phonetics.phonetic.
- The types involved
lib.natural.phonetics.soundex.SoundEx→lib.natural.phonetics.phonetic.Phonetic
- Direction
- lib.natural.phonetics.soundex uses lib.natural.phonetics.phonetic, so a change to lib.natural.phonetics.phonetic can break lib.natural.phonetics.soundex, while a change to lib.natural.phonetics.soundex can't break lib.natural.phonetics.phonetic.
- Position
- Below the diagonal: lib.natural.phonetics.soundex uses a module listed above it, which is the healthy direction.
19→7 lib.natural.stemmers.porter_stemmer_es uses lib.natural.stemmers.stemmer_de✕
- Connections
- 1 pair of types, where a type in lib.natural.stemmers.porter_stemmer_es uses a type in lib.natural.stemmers.stemmer_de.
- The types involved
lib.natural.stemmers.porter_stemmer_es.PorterStemmer→lib.natural.stemmers.stemmer_de.Stemmer
- Direction
- lib.natural.stemmers.porter_stemmer_es uses lib.natural.stemmers.stemmer_de, so a change to lib.natural.stemmers.stemmer_de can break lib.natural.stemmers.porter_stemmer_es, while a change to lib.natural.stemmers.porter_stemmer_es can't break lib.natural.stemmers.stemmer_de.
- Position
- Below the diagonal: lib.natural.stemmers.porter_stemmer_es uses a module listed above it, which is the healthy direction.
20→7 lib.natural.stemmers.porter_stemmer_nl uses lib.natural.stemmers.stemmer_de✕
- Connections
- 1 pair of types, where a type in lib.natural.stemmers.porter_stemmer_nl uses a type in lib.natural.stemmers.stemmer_de.
- The types involved
lib.natural.stemmers.porter_stemmer_nl.PorterStemmer→lib.natural.stemmers.stemmer_de.Stemmer
- Direction
- lib.natural.stemmers.porter_stemmer_nl uses lib.natural.stemmers.stemmer_de, so a change to lib.natural.stemmers.stemmer_de can break lib.natural.stemmers.porter_stemmer_nl, while a change to lib.natural.stemmers.porter_stemmer_nl can't break lib.natural.stemmers.stemmer_de.
- Position
- Below the diagonal: lib.natural.stemmers.porter_stemmer_nl uses a module listed above it, which is the healthy direction.
21→8 lib.natural.tokenizers.aggressive_tokenizer uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer, while a change to lib.natural.tokenizers.aggressive_tokenizer can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer uses a module listed above it, which is the healthy direction.
22→8 lib.natural.tokenizers.aggressive_tokenizer_de uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_de uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_de.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_de uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_de, while a change to lib.natural.tokenizers.aggressive_tokenizer_de can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_de uses a module listed above it, which is the healthy direction.
23→8 lib.natural.tokenizers.aggressive_tokenizer_es uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_es uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_es.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_es uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_es, while a change to lib.natural.tokenizers.aggressive_tokenizer_es can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_es uses a module listed above it, which is the healthy direction.
24→8 lib.natural.tokenizers.aggressive_tokenizer_fa uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_fa uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_fa.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_fa uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_fa, while a change to lib.natural.tokenizers.aggressive_tokenizer_fa can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_fa uses a module listed above it, which is the healthy direction.
25→8 lib.natural.tokenizers.aggressive_tokenizer_fr uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_fr uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_fr.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_fr uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_fr, while a change to lib.natural.tokenizers.aggressive_tokenizer_fr can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_fr uses a module listed above it, which is the healthy direction.
26→8 lib.natural.tokenizers.aggressive_tokenizer_hi uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_hi uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_hi.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_hi uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_hi, while a change to lib.natural.tokenizers.aggressive_tokenizer_hi can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_hi uses a module listed above it, which is the healthy direction.
27→8 lib.natural.tokenizers.aggressive_tokenizer_id uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_id uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_id.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_id uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_id, while a change to lib.natural.tokenizers.aggressive_tokenizer_id can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_id uses a module listed above it, which is the healthy direction.
28→8 lib.natural.tokenizers.aggressive_tokenizer_it uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_it uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_it.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_it uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_it, while a change to lib.natural.tokenizers.aggressive_tokenizer_it can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_it uses a module listed above it, which is the healthy direction.
29→8 lib.natural.tokenizers.aggressive_tokenizer_nl uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_nl uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_nl.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_nl uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_nl, while a change to lib.natural.tokenizers.aggressive_tokenizer_nl can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_nl uses a module listed above it, which is the healthy direction.
30→8 lib.natural.tokenizers.aggressive_tokenizer_no uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_no uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_no.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_no uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_no, while a change to lib.natural.tokenizers.aggressive_tokenizer_no can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_no uses a module listed above it, which is the healthy direction.
31→8 lib.natural.tokenizers.aggressive_tokenizer_pl uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_pl uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_pl.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_pl uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_pl, while a change to lib.natural.tokenizers.aggressive_tokenizer_pl can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_pl uses a module listed above it, which is the healthy direction.
32→8 lib.natural.tokenizers.aggressive_tokenizer_pt uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_pt uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_pt.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_pt uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_pt, while a change to lib.natural.tokenizers.aggressive_tokenizer_pt can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_pt uses a module listed above it, which is the healthy direction.
33→8 lib.natural.tokenizers.aggressive_tokenizer_ru uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_ru uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_ru.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_ru uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_ru, while a change to lib.natural.tokenizers.aggressive_tokenizer_ru can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_ru uses a module listed above it, which is the healthy direction.
34→8 lib.natural.tokenizers.aggressive_tokenizer_sv uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_sv uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_sv.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_sv uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_sv, while a change to lib.natural.tokenizers.aggressive_tokenizer_sv can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_sv uses a module listed above it, which is the healthy direction.
35→8 lib.natural.tokenizers.aggressive_tokenizer_uk uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_uk uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_uk.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_uk uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_uk, while a change to lib.natural.tokenizers.aggressive_tokenizer_uk can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_uk uses a module listed above it, which is the healthy direction.
36→8 lib.natural.tokenizers.aggressive_tokenizer_vi uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.aggressive_tokenizer_vi uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.aggressive_tokenizer_vi.AggressiveTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.aggressive_tokenizer_vi uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.aggressive_tokenizer_vi, while a change to lib.natural.tokenizers.aggressive_tokenizer_vi can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.aggressive_tokenizer_vi uses a module listed above it, which is the healthy direction.
37→8 lib.natural.tokenizers.regexp_tokenizer uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.regexp_tokenizer uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.regexp_tokenizer.RegexpTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.regexp_tokenizer uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.regexp_tokenizer, while a change to lib.natural.tokenizers.regexp_tokenizer can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.regexp_tokenizer uses a module listed above it, which is the healthy direction.
38→8 lib.natural.tokenizers.sentence_tokenizer uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.sentence_tokenizer uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.sentence_tokenizer.SentenceTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.sentence_tokenizer uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.sentence_tokenizer, while a change to lib.natural.tokenizers.sentence_tokenizer can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.sentence_tokenizer uses a module listed above it, which is the healthy direction.
39→8 lib.natural.tokenizers.sentence_tokenizer_deprecated uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.sentence_tokenizer_deprecated uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.sentence_tokenizer_deprecated.SentenceTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.sentence_tokenizer_deprecated uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.sentence_tokenizer_deprecated, while a change to lib.natural.tokenizers.sentence_tokenizer_deprecated can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.sentence_tokenizer_deprecated uses a module listed above it, which is the healthy direction.
40→8 lib.natural.tokenizers.tokenizer_case uses lib.natural.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in lib.natural.tokenizers.tokenizer_case uses a type in lib.natural.tokenizers.tokenizer.
- The types involved
lib.natural.tokenizers.tokenizer_case.CaseTokenizer→lib.natural.tokenizers.tokenizer.Tokenizer
- Direction
- lib.natural.tokenizers.tokenizer_case uses lib.natural.tokenizers.tokenizer, so a change to lib.natural.tokenizers.tokenizer can break lib.natural.tokenizers.tokenizer_case, while a change to lib.natural.tokenizers.tokenizer_case can't break lib.natural.tokenizers.tokenizer.
- Position
- Below the diagonal: lib.natural.tokenizers.tokenizer_case uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 33 | High / Critical |
| A05:2025 — Injection | 23 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a build/run (quick start) section to the root README — the first thing a newcomer needs; Resolve the 12 redundant comment finding(s) in Comment Value — start with Brill_POS_Trainer.js (3), stemmer_id.js (3), RuleTemplates.js.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.5 pts | Medium | Architecture documentation |
| Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with wordnet.js, index_file.js, REDACTED. | +2.3 pts | Low | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +4.7 pts | Medium | Documentation (README) |
| Resolve the 12 redundant comment finding(s) in Comment Value — start with Brill_POS_Trainer.js (3), stemmer_id.js (3), RuleTemplates.js. | +3.5 pts | Medium | Comment Value |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.8 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.8 pts | Low | Bus Factor |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MaxEntClassifier_spec.ts. | +1.6 pts | Low | Test Quality |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +0.8 pts | Low | Vulnerability-disclosure Policy |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| spec/MaxEntClassifier_spec.ts | 5.8 | Mixed | Test Quality: No assertions (empty test): Classifier does not need a correction feature |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| lib/natural/phonetics/double_metaphone.js | 7.0 | Mixed | Cyclomatic Complexity: DoubleMetaphone.process::handleC (cyclomatic 44) |
| lib/natural/stemmers/porter_stemmer_fr.js | 7.1 | Mixed | Cyclomatic Complexity: porter_stemmer_fr.stem (cyclomatic 70) |
| spec/stemmer_id_spec.ts | 7.3 | Mixed | Explicit Debt: TodoComment |
| lib/natural/stemmers/porter_stemmer_de.js | 7.4 | Mixed | Cyclomatic Complexity: porter_stemmer_de.stemm (cyclomatic 48) |
| lib/natural/stemmers/porter_stemmer_es.js | 7.4 | Mixed | Cyclomatic Complexity: PorterStemmer.stem (cyclomatic 42) |
| lib/natural/stemmers/porter_stemmer_nl.js | 7.4 | Mixed | Cyclomatic Complexity: PorterStemmer.step3b (cyclomatic 17) |
| lib/natural/stemmers/porter_stemmer_it.js | 7.8 | Mixed | Cyclomatic Complexity: porter_stemmer_it.PorterStemmer.stem (cyclomatic 34) |
| lib/natural/distance/levenshtein_distance.js | 7.8 | Mixed | Cyclomatic Complexity: levenshtein_distance.levenshteinDistance (cyclomatic 29) |
| lib/natural/stemmers/porter_stemmer_pt.js | 7.8 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 22) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 57 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 269 of 296 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs jasmine, which the coverage collector does not drive yet, so no lcov was produced — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`coverallsapp/github-action`) shows coverage is measured in your own CI.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jasmine via `npm ci --ignore-scripts` in the repository root (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (12668 LoC, 154 module-visible types across 30 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongoose' is imported (lib/natural/util/storage/MongoDB.js:24), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongoose' is imported (lib/natural/util/storage/MongoDB.js:24), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongoose' is imported (lib/natural/util/storage/MongoDB.js:24), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongoose' is imported (lib/natural/util/storage/MongoDB.js:24), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- P2 Observability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 38 further occurrence(s) are not listed individually; the score already reflects all 78.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 176 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index').
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
29 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was porter_stemmer_fr.stem at 70. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being porter_stemmer_fr.isVowel at 17 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with porter_stemmer_fr.stem (cyclomatic 70), porter_stemmer_de.stemm (cyclomatic 48), DoubleMetaphone.process::handleC (cyclomatic 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 5.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
44 method(s) exceeded the cognitive complexity threshold of 15; the worst was porter_stemmer_fr.stem at 100.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with porter_stemmer_fr.stem (cognitive 100), porter_stemmer_de.stemm (cognitive 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 3.7 to about 4.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with double_metaphone.js, porter_stemmer_es.js. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with porter_stemmer_fr.js, porter_stemmer_de.js. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 686 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MaxEntClassifier_spec.ts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 No assertions finding(s) in Test Quality — start with MaxEntClassifier_spec.ts (2), classifier_spec.ts. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
7 outdated direct production npm dependency(ies) of 14 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 50 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 50 package(s) this repository's committed lockfile installs for a consumer — its 14 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 24 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/natural/phonetics/double_metaphone.js. Counted over 22 of the 90 production source files in this repository: 56 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
2 deducted task-comment markers across 26 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with stemmer_id_spec.ts (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D24 · Comment Value
16 of 596 judged comments only repeat the code they sit on (2.7 %). 638 comment(s) in another language or script were not judged.
What to do
- Resolve the 12 redundant comment finding(s) in Comment Value — start with Brill_POS_Trainer.js (3), stemmer_id.js (3), RuleTemplates.js. — One of this dimension's main actionable groups (12 recommendation-level).
D27 · Navigability
12 % of calls cross a namespace and 0 % go through an interface, but 0 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 15 high, 8 medium, 0 low. 13 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 7 file(s) — `lib/natural/sentiment/Spanish/senticon_es.json`, `spec/test_data/snowball_de.json`, `spec/test_data/snowball_es.json`, `spec/test_data/snowball_fr.json`, `spec/test_data/snowball_it.json`, … (+2 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 13 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
24 finding(s): 1 critical, 15 high, 6 medium, 2 low.
What to do
- Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 4 high, 0 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
D34 · Knowledge Freshness
6 of 34 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/natural/wordnet/wordnet.js. Counted over 34 of the 90 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with wordnet.js, index_file.js, REDACTED. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but only routes reports to a public channel (no private reporting contact).
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `lib/natural/wordnet/data_file.js` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/data_file.js:33
- `lib/natural/wordnet/index_file.js` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/index_file.js:39
- `lib/natural/wordnet/index_file.js` reports through `console.*` at line 92 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/index_file.js:92
- `lib/natural/wordnet/wordnet.js` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/wordnet.js:140
- `lib/natural/wordnet/wordnet_file.js` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/wordnet_file.js:35
- `lib/natural/wordnet/wordnet_file.js` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/wordnet/wordnet_file.js:50
- `lib/natural/util/storage/Postgres.js` reports through `console.*` at line 68 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/util/storage/Postgres.js:68
- `lib/natural/util/storage/Postgres.js` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/util/storage/Postgres.js:84
- `lib/natural/util/storage/Postgres.js` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/util/storage/Postgres.js:96
- `lib/natural/util/storage/Postgres.js` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/util/storage/Postgres.js:100
- `REDACTED` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:37
- `lib/natural/tokenizers/regexp_tokenizer.js` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/regexp_tokenizer.js:64
- `lib/natural/tokenizers/regexp_tokenizer.js` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/regexp_tokenizer.js:71
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 160 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:160
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:161
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:164
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 168 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:168
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 172 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:172
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 176 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:176
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 180 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:180
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 187 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:187
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 190 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:190
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 193 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:193
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:194
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 195 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:195
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 196 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:196
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 197 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:197
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 198 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:198
- `lib/natural/tokenizers/sentence_tokenizer.js` reports through `console.*` at line 199 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer.js:199
- `lib/natural/tokenizers/sentence_tokenizer_deprecated.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer_deprecated.js:36
- `lib/natural/tokenizers/sentence_tokenizer_deprecated.js` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/tokenizers/sentence_tokenizer_deprecated.js:45
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:48
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 92 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:92
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 102 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:102
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 107 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:107
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 112 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:112
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 155 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:155
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 167 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:167
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 192 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:192
- `lib/natural/stemmers/porter_stemmer_nl.js` reports through `console.*` at line 205 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — lib/natural/stemmers/porter_stemmer_nl.js:205
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:13
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
- 66 typed · 186 plain JS — the untyped files are index.js, io_spec/MaxEntClassifier_spec.js, io_spec/Sample_spec.js, io_spec/StorageBackend_spec.js, io_spec/bayes_classifier_spec.js, io_spec/classifier_spec.js (+180 more).
R10 · Code Duplication
- REDACTED:27 · REDACTED:5 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:27
- lib/natural/util/longest_path_tree.js:37 · lib/natural/util/shortest_path_tree.js:37 — the two spans are one implementation copied and then locally edited — 359 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/util/longest_path_tree.js:37
- lib/natural/stemmers/indonesian/base_stemmer_id.js:28 · lib/natural/stemmers/stemmer.js:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — lib/natural/stemmers/indonesian/base_stemmer_id.js:28
- lib/natural/stemmers/indonesian/prefix_rules.js:111 · lib/natural/stemmers/indonesian/prefix_rules.js:547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/stemmers/indonesian/prefix_rules.js:111
- lib/natural/stemmers/indonesian/prefix_rules.js:324 · lib/natural/stemmers/indonesian/prefix_rules.js:373 · lib/natural/stemmers/indonesian/prefix_rules.js:461 · lib/natural/stemmers/indonesian/prefix_rules.js:606 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:324
- lib/natural/ngrams/ngrams.js:79 · lib/natural/ngrams/ngrams_zh.js:41 — the two spans are one implementation copied and then locally edited — 183 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/ngrams/ngrams.js:79
- lib/natural/stemmers/porter_stemmer_de.js:103 · lib/natural/stemmers/porter_stemmer_de.js:198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/stemmers/porter_stemmer_de.js:103
- lib/natural/classifiers/bayes_classifier.js:34 · lib/natural/classifiers/logistic_regression_classifier.js:31 — the two spans are one implementation copied and then locally edited — 125 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/classifiers/bayes_classifier.js:34
- lib/natural/stemmers/stemmer_de.js:30 · lib/natural/stemmers/stemmer_es.js:28 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — lib/natural/stemmers/stemmer_de.js:30
- lib/natural/stemmers/stemmer_it.js:26 · lib/natural/stemmers/stemmer_pl.js:28 · lib/natural/stemmers/stemmer_ru.js:28 · lib/natural/stemmers/stemmer_uk.js:6 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — lib/natural/stemmers/stemmer_it.js:26
- lib/natural/stemmers/stemmer_no.js:28 · lib/natural/stemmers/stemmer_sv.js:28 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — lib/natural/stemmers/stemmer_no.js:28
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js:525 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:583 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:525
- lib/natural/stemmers/indonesian/prefix_rules.js:423 · lib/natural/stemmers/indonesian/prefix_rules.js:698 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/stemmers/indonesian/prefix_rules.js:423
- lib/natural/stemmers/indonesian/prefix_rules.js:827 · lib/natural/stemmers/indonesian/prefix_rules.js:853 · lib/natural/stemmers/indonesian/prefix_rules.js:879 · lib/natural/stemmers/indonesian/prefix_rules.js:905 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:827
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js:360 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:466 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:360
- lib/natural/brill_pos_tagger/lib/Corpus.js:86 · lib/natural/classifiers/maxent/POS/ME_Corpus.js:41 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — lib/natural/brill_pos_tagger/lib/Corpus.js:86
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js:381 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:507 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:381
- lib/natural/stemmers/stemmer_es.js:33 · lib/natural/stemmers/stemmer_nl.js:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — lib/natural/stemmers/stemmer_es.js:33
- lib/natural/tokenizers/aggressive_tokenizer_pl.js:23 · lib/natural/tokenizers/aggressive_tokenizer_ru.js:23 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- lib/natural/tokenizers/aggressive_tokenizer_pl.js:23 · lib/natural/tokenizers/aggressive_tokenizer_uk.js:24 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- lib/natural/tokenizers/aggressive_tokenizer_ru.js:23 · lib/natural/tokenizers/aggressive_tokenizer_uk.js:24 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_ru.js:23
- lib/natural/classifiers/maxent/POS/POS_Element.js:46 · lib/natural/classifiers/maxent/POS/POS_Element.js:136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/classifiers/maxent/POS/POS_Element.js:46
- lib/natural/stemmers/indonesian/prefix_rules.js:242 · lib/natural/stemmers/indonesian/prefix_rules.js:783 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:242
- lib/natural/stemmers/indonesian/prefix_rules.js:289 · lib/natural/stemmers/indonesian/prefix_rules.js:350 · lib/natural/stemmers/indonesian/prefix_rules.js:399 · lib/natural/stemmers/indonesian/prefix_rules.js:589 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:289
- lib/natural/inflectors/fr/noun_inflector.js:204 · lib/natural/inflectors/ja/noun_inflector.js:101 · lib/natural/inflectors/noun_inflector.js:141 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/inflectors/fr/noun_inflector.js:204
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js:275 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:343 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:551 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:567 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:275
- lib/natural/stemmers/indonesian/prefix_rules.js:169 · lib/natural/stemmers/indonesian/prefix_rules.js:272 · lib/natural/stemmers/indonesian/prefix_rules.js:506 · lib/natural/stemmers/indonesian/prefix_rules.js:793 · +5 more site(s) not listed — all 9 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:169
- lib/natural/stemmers/indonesian/prefix_rules.js:931 · lib/natural/stemmers/indonesian/prefix_rules.js:948 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:931
- lib/natural/tokenizers/aggressive_tokenizer_pl.js:23 · lib/natural/tokenizers/aggressive_tokenizer_pt.js:23 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- lib/natural/tokenizers/aggressive_tokenizer_pt.js:23 · lib/natural/tokenizers/aggressive_tokenizer_ru.js:23 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_pt.js:23
- lib/natural/tokenizers/aggressive_tokenizer_pt.js:23 · lib/natural/tokenizers/aggressive_tokenizer_uk.js:24 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/tokenizers/aggressive_tokenizer_pt.js:23
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js:481 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:521 · lib/natural/brill_pos_tagger/lib/RuleTemplates.js:579 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:481
- lib/natural/classifiers/classifier.js:145 · lib/natural/classifiers/maxent/Classifier.js:75 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/classifiers/classifier.js:145
- lib/natural/stemmers/indonesian/base_stemmer_id.js:31 · lib/natural/stemmers/stemmer.js:31 · lib/natural/stemmers/stemmer_no.js:31 · lib/natural/stemmers/stemmer_pt.js:30 · +1 more site(s) not listed — the 5 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 5 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — lib/natural/stemmers/indonesian/base_stemmer_id.js:31
- lib/natural/stemmers/indonesian/prefix_rules.js:212 · lib/natural/stemmers/indonesian/prefix_rules.js:252 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/indonesian/prefix_rules.js:212
- lib/natural/stemmers/porter_stemmer_es.js:193 · lib/natural/stemmers/porter_stemmer_es.js:208 · lib/natural/stemmers/porter_stemmer_it.js:183 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/stemmers/porter_stemmer_es.js:193
- lib/natural/tfidf/tfidf.js:124 · lib/natural/tfidf/tfidf.js:167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/tfidf/tfidf.js:124
- lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:266 · lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:266
- lib/natural/util/storage/Memcached.js:33 · REDACTED:38 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/natural/util/storage/Memcached.js:33
- lib/natural/normalizers/normalizer_ja.js:584 · lib/natural/normalizers/normalizer_ja.js:607 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/natural/normalizers/normalizer_ja.js:584
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- stem has cyclomatic complexity 70 and cognitive complexity 100; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_fr.js:48
- stemm has cyclomatic complexity 48 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_de.js:24
- handleC has cyclomatic complexity 44 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/phonetics/double_metaphone.js:156
- stem has cyclomatic complexity 42 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_es.js:96
- process has cyclomatic complexity 38 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/phonetics/double_metaphone.js:32
- stem has cyclomatic complexity 34 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_it.js:82
- levenshteinDistance has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/distance/levenshtein_distance.js:122
- handleG has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/phonetics/double_metaphone.js:256
- handleS has cyclomatic complexity 23 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/phonetics/double_metaphone.js:378
- regions has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_fr.js:264
- step3b has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_nl.js:265
- tokenize has cyclomatic complexity 17 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/tokenizers/sentence_tokenizer.js:155
- ngrams has cyclomatic complexity 15 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/ngrams/ngrams.js:73
- distance has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/distance/jaro-winkler_distance.js:31
- type has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/analyzers/sentence_analyzer.js:145
- markRegions has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_nl.js:118
- prelude has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/stemmers/porter_stemmer_fr.js:314
- stem has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — REDACTED:112, REDACTED:88
- handleJ has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/phonetics/double_metaphone.js:314
- ngrams has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/ngrams/ngrams_zh.js:37
- trainParallelBatches has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/natural/classifiers/classifier_train_parallel.js:144
R3 · Large Files
- lib/natural/stemmers/indonesian/prefix_rules.js has 856 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/stemmers/indonesian/prefix_rules.js:1
- lib/natural/stemmers/lancaster_rules.js has 786 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/stemmers/lancaster_rules.js:1
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js has 654 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/brill_pos_tagger/lib/RuleTemplates.js:1
- spec/double_metaphone_spec.ts has 649 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spec/double_metaphone_spec.ts:1
- lib/natural/brill_pos_tagger/lib/TF_Parser.js has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/brill_pos_tagger/lib/TF_Parser.js:1
- lib/natural/normalizers/normalizer_ja.js has 606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/normalizers/normalizer_ja.js:1
- lib/natural/transliterators/ja/index.js has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/transliterators/ja/index.js:1
- lib/natural/phonetics/double_metaphone.js has 456 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/natural/phonetics/double_metaphone.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×7) — lib/natural/util/stopwords_pl.js:1, lib/natural/stemmers/stemmer_pl.js:1, lib/natural/sentiment/tools/sentimentXmlParser.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- Unreachable from the 7 application, 20 tooling and 78 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (7 application, 20 tooling, 78 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (lib/natural/stemmers/stemmer_pl.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — lib/natural/util/stopwords_pl.js
- no import path from any entry point (7 application, 20 tooling, 78 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — lib/natural/stemmers/stemmer_pl.js, lib/natural/sentiment/tools/sentimentXmlParser.js, lib/natural/sentiment/tools/XmlParser4PatternData.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×5)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by D2, R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 50% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63% | Adequate | Acceptable, with room to improve. |
| Security | 62% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'mongoose' (lib/natural/util/storage/MongoDB.js:24) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'mongoose' (lib/natural/util/storage/MongoDB.js:24) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'mongoose' (lib/natural/util/storage/MongoDB.js:24) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: this repository stores data through 'mongoose' (lib/natural/util/storage/MongoDB.js:24) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D11 Test Reliability — No tests discovered
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1708 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D4 Code Duplication — This repository's production source (.js, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 176 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 36 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): Classifier does not need a correction feature spec/MaxEntClassifier_spec.ts:78
- REDACTED
- REDACTED
- REDACTED
Serious — 159 finding(s)
- No test reaches this file lib/natural/util/stopwords_pl.js:1
- No test reaches this file lib/natural/stemmers/stemmer_pl.js:1
- No test reaches this file lib/natural/sentiment/tools/sentimentXmlParser.js:1
- No test reaches this file lib/natural/sentiment/tools/XmlParser4PatternData.js:1
- No test reaches this file lib/natural/tokenizers/sentence_tokenizer_deprecated.js:1
- No test reaches this file lib/natural/util/stopwords_zh.js:1
- No test reaches this file index.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- DoubleMetaphone.process::handleC (cyclomatic 44) lib/natural/phonetics/double_metaphone.js:156
- DoubleMetaphone.process::handleG (cyclomatic 26) lib/natural/phonetics/double_metaphone.js:256
- DoubleMetaphone.process::handleS (cyclomatic 23) lib/natural/phonetics/double_metaphone.js:378
- No assertions: Save classifer to a file spec/MaxEntClassifier_spec.ts:92
- No assertions: Load classifer spec/MaxEntClassifier_spec.ts:104
- No assertions: should emit events when documents are added or training is finished spec/classifier_spec.ts:62
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2 locations) lib/natural/brill_pos_tagger/lib/Corpus.js:86
- Duplicated block (14 lines × 2 locations) lib/natural/brill_pos_tagger/lib/RuleTemplates.js:381
- Duplicated block (14 lines × 2 locations) lib/natural/stemmers/stemmer_es.js:33
- Duplicated block with local edits (14 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- Duplicated block with local edits (14 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- Duplicated block with local edits (14 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_ru.js:23
- Duplicated block with local edits (11 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_pl.js:23
- Duplicated block with local edits (11 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_pt.js:23
- Duplicated block with local edits (11 matched lines × 2 locations) lib/natural/tokenizers/aggressive_tokenizer_pt.js:23
- Deprecated: eslint package.json:37
- Deprecated: eslint-config-standard-with-typescript package.json:38
- TodoComment spec/stemmer_id_spec.ts:220
- TodoComment spec/stemmer_id_spec.ts:333
- DoubleMetaphone.process::handleG (cognitive 35) lib/natural/phonetics/double_metaphone.js:256
- DoubleMetaphone.process::handleS (cognitive 32) lib/natural/phonetics/double_metaphone.js:378
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: DoubleMetaphone.process lib/natural/phonetics/double_metaphone.js:32
- MethodTooLong: PorterStemmer.stem lib/natural/stemmers/porter_stemmer_es.js:96
- FunctionTooLong: porter_stemmer_fr.stem lib/natural/stemmers/porter_stemmer_fr.js:48
- FunctionTooLong: porter_stemmer_de.stemm lib/natural/stemmers/porter_stemmer_de.js:24
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2 locations) lib/natural/brill_pos_tagger/lib/RuleTemplates.js:525
- Duplicated block (18 lines × 2 locations) lib/natural/stemmers/indonesian/prefix_rules.js:423
- Duplicated block (13 lines × 2 locations) lib/natural/classifiers/maxent/POS/POS_Element.js:46
- Duplicated block (13 lines × 2 locations) lib/natural/stemmers/indonesian/prefix_rules.js:242
- Duplicated block (10 lines × 3 locations) lib/natural/brill_pos_tagger/lib/RuleTemplates.js:481
- Duplicated block (10 lines × 3 locations) lib/natural/stemmers/porter_stemmer_es.js:193
- Duplicated block (10 lines × 2 locations) lib/natural/stemmers/indonesian/prefix_rules.js:212
- Duplicated block (10 lines × 2 locations) lib/natural/tfidf/tfidf.js:124
- Complex function stem (cyclomatic 12, cognitive 19) REDACTED:112
- Complex function stem (cyclomatic 12, cognitive 19) REDACTED:88
- porter_stemmer_fr.stem (cyclomatic 70) lib/natural/stemmers/porter_stemmer_fr.js:48
- porter_stemmer_de.stemm (cyclomatic 48) lib/natural/stemmers/porter_stemmer_de.js:24
- PorterStemmer.stem (cyclomatic 42) lib/natural/stemmers/porter_stemmer_es.js:96
- DoubleMetaphone.process (cyclomatic 38) lib/natural/phonetics/double_metaphone.js:32
- porter_stemmer_it.PorterStemmer.stem (cyclomatic 34) lib/natural/stemmers/porter_stemmer_it.js:82
- levenshtein_distance.levenshteinDistance (cyclomatic 29) lib/natural/distance/levenshtein_distance.js:122
- (anonymous) (cyclomatic 22) lib/natural/stemmers/porter_stemmer_pt.js:25
- classifier_train_parallel.trainParallelBatches (cyclomatic 20) lib/natural/classifiers/classifier_train_parallel.js:144
- SentenceTokenizer.tokenize (cyclomatic 18) lib/natural/tokenizers/sentence_tokenizer.js:155
- porter_stemmer_fr.regions (cyclomatic 17) lib/natural/stemmers/porter_stemmer_fr.js:264
- PorterStemmer.step3b (cyclomatic 17) lib/natural/stemmers/porter_stemmer_nl.js:265
- ngrams.ngrams (cyclomatic 16) lib/natural/ngrams/ngrams.js:73
- porter_stemmer_fr.stem (cognitive 100) lib/natural/stemmers/porter_stemmer_fr.js:48
- porter_stemmer_de.stemm (cognitive 80) lib/natural/stemmers/porter_stemmer_de.js:24
- PorterStemmer.stem (cognitive 58) lib/natural/stemmers/porter_stemmer_es.js:96
- process::handleC (cognitive 57) lib/natural/phonetics/double_metaphone.js:156
- porter_stemmer_it.PorterStemmer.stem (cognitive 40) lib/natural/stemmers/porter_stemmer_it.js:82
- levenshtein_distance.levenshteinDistance (cognitive 35) lib/natural/distance/levenshtein_distance.js:122
- ngrams.ngrams (cognitive 26) lib/natural/ngrams/ngrams.js:73
- SentenceAnalyzer.part (cognitive 22) lib/natural/analyzers/sentence_analyzer.js:54
- lancaster_stemmer.applyRuleSection (cognitive 22) lib/natural/stemmers/lancaster_stemmer.js:33
- step1b (cognitive 22) REDACTED:116
- (anonymous) (cognitive 22) lib/natural/stemmers/porter_stemmer_pt.js:25
- classifier_train_parallel.trainParallelBatches (cognitive 21) lib/natural/classifiers/classifier_train_parallel.js:144
- jaro-winkler_distance.distance (cognitive 21) lib/natural/distance/jaro-winkler_distance.js:31
- porter_stemmer_fr.regions (cognitive 21) lib/natural/stemmers/porter_stemmer_fr.js:264
- type (cognitive 20) lib/natural/analyzers/sentence_analyzer.js:145
- step3b (cognitive 20) lib/natural/stemmers/porter_stemmer_nl.js:265
- porter_stemmer_uk.PorterStemmer.stem (cognitive 19) REDACTED:88
- porter_stemmer_ru.PorterStemmer.stem (cognitive 19) REDACTED:112
- PorterStemmer.markRegions (cognitive 18) lib/natural/stemmers/porter_stemmer_nl.js:118
- SentenceTokenizer.tokenize (cognitive 17) lib/natural/tokenizers/sentence_tokenizer.js:155
- SentimentAnalyzer.constructor (cognitive 16) lib/natural/sentiment/SentimentAnalyzer.js:85
- SentimentAnalyzer.getSentiment (cognitive 16) lib/natural/sentiment/SentimentAnalyzer.js:132
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Coverage collected but not gated
- Type Safety
- Wholesale file copy (61 identical lines × 2 files) REDACTED:27
- Duplicated block with local edits (51 matched lines × 2 locations) lib/natural/util/longest_path_tree.js:37
- Duplicated block (38 lines × 2 locations) lib/natural/stemmers/indonesian/base_stemmer_id.js:28
- Duplicated block (34 lines × 2 locations) lib/natural/stemmers/indonesian/prefix_rules.js:111
- Duplicated block (22 lines × 6 locations) lib/natural/stemmers/indonesian/prefix_rules.js:324
- Duplicated block with local edits (21 matched lines × 2 locations) lib/natural/ngrams/ngrams.js:79
- Duplicated block (21 lines × 2 locations) lib/natural/stemmers/porter_stemmer_de.js:103
- Duplicated block with local edits (20 matched lines × 2 locations) lib/natural/classifiers/bayes_classifier.js:34
- Duplicated block (20 lines × 2 locations) lib/natural/stemmers/stemmer_de.js:30
- Duplicated block (19 lines × 4 locations) lib/natural/stemmers/stemmer_it.js:26
- Duplicated block (19 lines × 2 locations) lib/natural/stemmers/stemmer_no.js:28
- Duplicated block (17 lines × 4 locations) lib/natural/stemmers/indonesian/prefix_rules.js:827
- Duplicated block (15 lines × 2 locations) lib/natural/brill_pos_tagger/lib/RuleTemplates.js:360
- Duplicated block (13 lines × 6 locations) lib/natural/stemmers/indonesian/prefix_rules.js:289
- Duplicated block (12 lines × 3 locations) lib/natural/inflectors/fr/noun_inflector.js:204
- Duplicated block (11 lines × 4 locations) lib/natural/brill_pos_tagger/lib/RuleTemplates.js:275
- Duplicated block (11 lines × 9 locations) lib/natural/stemmers/indonesian/prefix_rules.js:169
- Duplicated block (11 lines × 2 locations) lib/natural/stemmers/indonesian/prefix_rules.js:931
- Duplicated block with local edits (10 matched lines × 2 locations) lib/natural/classifiers/classifier.js:145
- Duplicated block (10 lines × 5 locations) lib/natural/stemmers/indonesian/base_stemmer_id.js:31
- Duplicated block (9 lines × 2 locations) lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:266
- Duplicated block with local edits (9 matched lines × 2 locations) lib/natural/util/storage/Memcached.js:33
- Duplicated block (8 lines × 2 locations) lib/natural/normalizers/normalizer_ja.js:584
- Complex function stem (cyclomatic 70, cognitive 100) lib/natural/stemmers/porter_stemmer_fr.js:48
- Complex function stemm (cyclomatic 48, cognitive 80) lib/natural/stemmers/porter_stemmer_de.js:24
- Complex function handleC (cyclomatic 44, cognitive 57) lib/natural/phonetics/double_metaphone.js:156
- Complex function stem (cyclomatic 42, cognitive 58) lib/natural/stemmers/porter_stemmer_es.js:96
- Complex function process (cyclomatic 38, cognitive 11) lib/natural/phonetics/double_metaphone.js:32
- Complex function stem (cyclomatic 34, cognitive 40) lib/natural/stemmers/porter_stemmer_it.js:82
- Complex function levenshteinDistance (cyclomatic 29, cognitive 35) lib/natural/distance/levenshtein_distance.js:122
- Complex function handleG (cyclomatic 26, cognitive 35) lib/natural/phonetics/double_metaphone.js:256
- Complex function handleS (cyclomatic 23, cognitive 32) lib/natural/phonetics/double_metaphone.js:378
- Complex function regions (cyclomatic 17, cognitive 21) lib/natural/stemmers/porter_stemmer_fr.js:264
- Complex function step3b (cyclomatic 17, cognitive 20) lib/natural/stemmers/porter_stemmer_nl.js:265
- Complex function tokenize (cyclomatic 17, cognitive 11) lib/natural/tokenizers/sentence_tokenizer.js:155
- Complex function ngrams (cyclomatic 15, cognitive 24) lib/natural/ngrams/ngrams.js:73
- Complex function distance (cyclomatic 14, cognitive 21) lib/natural/distance/jaro-winkler_distance.js:31
- Complex function type (cyclomatic 14, cognitive 20) lib/natural/analyzers/sentence_analyzer.js:145
- Complex function markRegions (cyclomatic 13, cognitive 18) lib/natural/stemmers/porter_stemmer_nl.js:118
- Complex function prelude (cyclomatic 13, cognitive 14) lib/natural/stemmers/porter_stemmer_fr.js:314
- Complex function handleJ (cyclomatic 12, cognitive 15) lib/natural/phonetics/double_metaphone.js:314
- Complex function ngrams (cyclomatic 11, cognitive 14) lib/natural/ngrams/ngrams_zh.js:37
- Complex function trainParallelBatches (cyclomatic 11, cognitive 12) lib/natural/classifiers/classifier_train_parallel.js:144
- lib/natural/stemmers/indonesian/prefix_rules.js: 856 lines of code lib/natural/stemmers/indonesian/prefix_rules.js:1
- lib/natural/stemmers/lancaster_rules.js: 786 lines of code lib/natural/stemmers/lancaster_rules.js:1
- lib/natural/brill_pos_tagger/lib/RuleTemplates.js: 654 lines of code lib/natural/brill_pos_tagger/lib/RuleTemplates.js:1
- spec/double_metaphone_spec.ts: 649 lines of code spec/double_metaphone_spec.ts:1
- lib/natural/brill_pos_tagger/lib/TF_Parser.js: 642 lines of code lib/natural/brill_pos_tagger/lib/TF_Parser.js:1
- lib/natural/normalizers/normalizer_ja.js: 606 lines of code lib/natural/normalizers/normalizer_ja.js:1
- lib/natural/transliterators/ja/index.js: 513 lines of code lib/natural/transliterators/ja/index.js:1
- lib/natural/phonetics/double_metaphone.js: 456 lines of code lib/natural/phonetics/double_metaphone.js:1
- Dead file (~64 LoC) lib/natural/util/stopwords_pl.js
- Dead file (~63 LoC) lib/natural/stemmers/stemmer_pl.js
- Dead file (~57 LoC) lib/natural/sentiment/tools/sentimentXmlParser.js
- Dead file (~56 LoC) lib/natural/sentiment/tools/XmlParser4PatternData.js
- Dead file (~51 LoC) lib/natural/tokenizers/sentence_tokenizer_deprecated.js
- Dead file (~47 LoC) lib/natural/util/stopwords_zh.js
- Unused dependency 'ncp'
- Unused dependency 'pegjs'
- Unused dependency 'proxyquire'
- Unused dependency 'source-map-support'
- Unused dependency 'sylvester'
Minor — 93 finding(s)
- Console output used as the logging channel lib/natural/wordnet/data_file.js:33
- Console output used as the logging channel lib/natural/wordnet/index_file.js:39
- Console output used as the logging channel lib/natural/wordnet/index_file.js:92
- Console output used as the logging channel lib/natural/wordnet/wordnet.js:140
- Console output used as the logging channel lib/natural/wordnet/wordnet_file.js:35
- Console output used as the logging channel lib/natural/wordnet/wordnet_file.js:50
- Console output used as the logging channel lib/natural/util/storage/Postgres.js:68
- Console output used as the logging channel lib/natural/util/storage/Postgres.js:84
- Console output used as the logging channel lib/natural/util/storage/Postgres.js:96
- Console output used as the logging channel lib/natural/util/storage/Postgres.js:100
- Console output used as the logging channel REDACTED:37
- Console output used as the logging channel lib/natural/tokenizers/regexp_tokenizer.js:64
- Console output used as the logging channel lib/natural/tokenizers/regexp_tokenizer.js:71
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:160
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:161
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:164
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:168
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:172
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:176
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:180
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:187
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:190
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:193
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:194
- Console output used as the logging channel lib/natural/tokenizers/sentence_tokenizer.js:195
- Deprecated: @humanwhocodes/config-array REDACTED:442
- Deprecated: @humanwhocodes/object-schema REDACTED:496
- Deprecated: glob REDACTED:3369
- Deprecated: rimraf REDACTED:3404
- Deprecated: inflight REDACTED:3921
- Deprecated: glob REDACTED:4532
- Deprecated: rimraf REDACTED:4567
- Deprecated: glob REDACTED:5279
- Deprecated: rimraf REDACTED:5366
- Deprecated: glob REDACTED:6229
- Deprecated: glob REDACTED:6774
- Deprecated: rimraf REDACTED:6809
- Deprecated: glob REDACTED:7065
- redundant comment lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:135
- redundant comment lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:144
- redundant comment lib/natural/brill_pos_tagger/lib/Brill_POS_Trainer.js:342
- redundant comment lib/natural/brill_pos_tagger/lib/RuleTemplates.js:357
- redundant comment lib/natural/brill_pos_tagger/lib/TransformationRule.js:70
- redundant comment lib/natural/inflectors/singular_plural_inflector.js:79
- redundant comment lib/natural/normalizers/normalizer.js:63
- redundant comment lib/natural/stemmers/indonesian/stemmer_id.js:61
- redundant comment lib/natural/stemmers/indonesian/stemmer_id.js:93
- redundant comment lib/natural/stemmers/indonesian/stemmer_id.js:212
- redundant comment lib/natural/stemmers/token.js:60
- redundant comment spec/noun_inflector_fr_spec.ts:167
- Duplicated predicate lib/natural/stemmers/porter_stemmer_fr.js:272
- Duplicated predicate lib/natural/stemmers/stemmer_es.js:38
- Duplicated predicate lib/natural/stemmers/stemmer_no.js:47
- Duplicated predicate REDACTED:148
- Duplicated predicate lib/natural/distance/hamming_distance.js:32
- Duplicated predicate lib/natural/ngrams/ngrams.js:113
- Duplicated predicate lib/natural/ngrams/ngrams.js:85
- Orphaned file lib/natural/wordnet/wordnet.js:1
- Orphaned file lib/natural/wordnet/index_file.js:1
- Orphaned file REDACTED:1
- Orphaned file lib/natural/wordnet/data_file.js:1
- Orphaned file lib/natural/stemmers/lancaster_stemmer.js:1
- Orphaned file lib/natural/util/stopwords.js:1
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No dependency-update automation package.json:13
- No rollback/health safety
- No changelog
Minor — 8 finding(s)
- Outdated (npm): dotenv
- Outdated (npm): mongoose
- Outdated (npm): pg
- Outdated (npm): redis
- Outdated (npm): safe-stable-stringify
- Outdated (npm): underscore
- Outdated (npm): uuid
- doc comments repeat the names lib/natural/normalizers/normalizer_ja.js:591
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3827ebb287ea4910b99b3ac7f6fb978d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3827ebb287ea4910b99b3ac7f6fb978d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 24 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |