|
| 1 | +# npcheck review - April 15 2024 |
| 2 | + |
| 3 | +No major concerns were noted in this review. |
| 4 | + |
| 5 | +## Diff in npcheck.json since last review |
| 6 | + |
| 7 | +Only change was to move the location of node-rdkafka in the file, no |
| 8 | +material change. |
| 9 | + |
| 10 | +diff --git a/npcheck.json b/npcheck.json |
| 11 | +index d220594..1f65eff 100644 |
| 12 | +--- a/npcheck.json |
| 13 | ++++ b/npcheck.json |
| 14 | +@@ -1,5 +1,15 @@ |
| 15 | + { |
| 16 | + "modules": [ |
| 17 | ++ { |
| 18 | ++ "name": "node-rdkafka", |
| 19 | ++ "npmlink": "https://www.npmjs.com/package/node-rdkafka", |
| 20 | ++ "reviewlevel": "Active Watch", |
| 21 | ++ "activitycurrent": "None", |
| 22 | ++ "activitytarget": "Tested and Verified", |
| 23 | ++ "section": [ |
| 24 | ++ "Message Queuing" |
| 25 | ++ ] |
| 26 | ++ }, |
| 27 | + { |
| 28 | + "name": "cldr-localenames-full", |
| 29 | + "npmLink": "https://npmjs.com/package/cldr-localenames-full", |
| 30 | +@@ -115,16 +125,6 @@ |
| 31 | + "Message Queuing" |
| 32 | + ] |
| 33 | + }, |
| 34 | +- { |
| 35 | +- "name": "node-rdkafka", |
| 36 | +- "npmlink": "https://www.npmjs.com/package/node-rdkafka", |
| 37 | +- "reviewlevel": "Active Watch", |
| 38 | +- "activitycurrent": "None", |
| 39 | +- "activitytarget": "Tested and Verified", |
| 40 | +- "section": [ |
| 41 | +- "Message Queuing" |
| 42 | +- ] |
| 43 | +- }, |
| 44 | + { |
| 45 | + "name": "opossum", |
| 46 | + "npmlink": "https://www.npmjs.com/package/opossum", |
| 47 | + |
| 48 | + |
| 49 | +## Results |
| 50 | + |
| 51 | +https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/8695409976 |
| 52 | + |
| 53 | +npcheck report |
| 54 | + |
| 55 | +```shell |
| 56 | +(1): The module "node-rdkafka" seems to have no available TypeScript typings. |
| 57 | +(2): The "cldr-localenames-full" seems that is lacking appropriate testing (https://www.github.com/unicode-cldr/cldr-json) |
| 58 | +(3): The module "cldr-localenames-full" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 59 | +(4): The module "cldr-localenames-full" seems to have no available TypeScript typings. |
| 60 | +(5): The module "eslint" seems to have no available TypeScript typings. |
| 61 | +(6): The module "eslint" has "87" dependencies (including sub-dependencies) which is more than the default "20". |
| 62 | +(7): The module "express" seems to have no available TypeScript typings. |
| 63 | +(8): The module "express" has "62" dependencies (including sub-dependencies) which is more than the default "20". |
| 64 | +(9): The module "express-prom-bundle" has "80" dependencies (including sub-dependencies) which is more than the default "20". |
| 65 | +(10): The latest release of "ibmcloud-appid" was about 1 year ago |
| 66 | +(11): The module "ibmcloud-appid" has "227" dependencies (including sub-dependencies) which is more than the default "20". |
| 67 | +(12): The module "i18next" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 68 | +(13): The module "i18next" is not tested by community CITGM runs. |
| 69 | +(14): The latest release of "i18next-icu" was about 1 year ago |
| 70 | +(15): The module "i18next-icu" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 71 | +(16): The module "i18next-http-middleware" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 72 | +(17): The module "i18next-fs-backend" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 73 | +(18): The latest release of "ioredis" was about 1 year ago |
| 74 | +(19): The module "ioredis" is not tested by community CITGM runs. |
| 75 | +(20): The module "opossum" seems to have no available TypeScript typings. |
| 76 | +(21): The module "passport" seems to have no available TypeScript typings. |
| 77 | +(22): The module "pino" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 78 | +(23): The module "pino" has "22" dependencies (including sub-dependencies) which is more than the default "20". |
| 79 | +(24): The latest release of "rhea" was about 1 year ago |
| 80 | +(25): The module "rhea" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 81 | +(26): The module "mocha" seems to have no available TypeScript typings. |
| 82 | +(27): The module "mocha" has "69" dependencies (including sub-dependencies) which is more than the default "20". |
| 83 | +(28): The "jest" seems that is lacking appropriate testing (https://www.github.com/jestjs/jest) |
| 84 | +(29): The module "jest" has "261" dependencies (including sub-dependencies) which is more than the default "20". |
| 85 | +(30): The module "@ibm-cloud/cloudant" has "97" dependencies (including sub-dependencies) which is more than the default "20". |
| 86 | +(31): The module "nano" has "25" dependencies (including sub-dependencies) which is more than the default "20". |
| 87 | +(32): The latest release of "odbc" was 11 months ago |
| 88 | +(33): The module "odbc" has "57" dependencies (including sub-dependencies) which is more than the default "20". |
| 89 | +(34): The module "ibm_db" seems to have no available TypeScript typings. |
| 90 | +(35): The module "ibm_db" has "45" dependencies (including sub-dependencies) which is more than the default "20". |
| 91 | +(36): The module "mongodb" is not tested by community CITGM runs. |
| 92 | +(37): The module "pg" seems to have no available TypeScript typings. |
| 93 | +(38): The module "pg" is not tested by community CITGM runs. |
| 94 | +(39): The latest release of "kafkajs" was about 1 year ago |
| 95 | +(40): The "@openapitools/openapi-generator-cli" seems that is lacking appropriate testing (https://www.github.com/OpenAPITools/openapi-generator-cli) |
| 96 | +(41): The module "@openapitools/openapi-generator-cli" seems to have no available TypeScript typings. |
| 97 | +(42): The module "@openapitools/openapi-generator-cli" has "107" dependencies (including sub-dependencies) which is more than the default "20". |
| 98 | +(43): The module "openapi-backend" has "35" dependencies (including sub-dependencies) which is more than the default "20". |
| 99 | +(44): The module "@stoplight/prism-cli" is not tested by community CITGM runs. |
| 100 | +(45): The module "@stoplight/prism-cli" has "176" dependencies (including sub-dependencies) which is more than the default "20". |
| 101 | +(46): The module "express-openapi-validator" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 102 | +(47): The module "express-openapi-validator" has "55" dependencies (including sub-dependencies) which is more than the default "20". |
| 103 | +(48): The module "swagger-editor" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 104 | +(49): The module "swagger-editor" seems to have no available TypeScript typings. |
| 105 | +(50): The module "swagger-editor" has "375" dependencies (including sub-dependencies) which is more than the default "20". |
| 106 | +(51): The latest release of "openapi-editor" was over 3 years ago |
| 107 | +(52): The module "openapi-editor" has "200" dependencies (including sub-dependencies) which is more than the default "20". |
| 108 | +(53): The latest release of "nyc" was almost 4 years ago |
| 109 | +(54): The module "nyc" seems to have no available TypeScript typings. |
| 110 | +(55): The module "nyc" is not tested by community CITGM runs. |
| 111 | +(56): The module "nyc" has "145" dependencies (including sub-dependencies) which is more than the default "20". |
| 112 | +(57): The module "dotenv" is not tested by community CITGM runs. |
| 113 | +(58): The latest release of "node-vault" was 9 months ago |
| 114 | +(59): The module "node-vault" seems to have no available TypeScript typings. |
| 115 | +(60): The module "node-vault" is not tested by community CITGM runs. |
| 116 | +(61): The module "node-vault" has "59" dependencies (including sub-dependencies) which is more than the default "20". |
| 117 | +(62): The module "@ibm-cloud/secrets-manager" seems to have no available TypeScript typings. |
| 118 | +(63): The module "@ibm-cloud/secrets-manager" is not tested by community CITGM runs. |
| 119 | +(64): The module "@ibm-cloud/secrets-manager" has "96" dependencies (including sub-dependencies) which is more than the default "20". |
| 120 | +(65): The module "@opentelemetry/sdk-trace-base" is not tested by community CITGM runs. |
| 121 | +(66): The module "@opentelemetry/sdk-trace-node" is not tested by community CITGM runs. |
| 122 | +(67): The module "axios" does not specify the engines field or package-support.json, so we cannot determine if it supports the LTS versions of Node.js. |
| 123 | +(68): The module "axios" is not tested by community CITGM runs. |
| 124 | +(69): The latest release of "node-fetch" was 8 months ago |
| 125 | +(70): The module "node-fetch" is not tested by community CITGM runs. |
| 126 | +(71): The latest release of "cors" was over 5 years ago |
| 127 | +(72): The module "cors" seems to have no available TypeScript typings. |
| 128 | +(73): The module "cors" is not tested by community CITGM runs. |
| 129 | + |
| 130 | +problems: 73 (errors: 0 - warnings: 73) |
| 131 | +``` |
| 132 | +
|
| 133 | +New (materially) since last review (excluding ones were # deps was already over limit and changed): |
| 134 | +``` |
| 135 | +None |
| 136 | +``` |
| 137 | +## Notes |
| 138 | +
|
| 139 | +There were releases of both express and mocha in the last 3 months with these from the last report |
| 140 | +no longer being reported |
| 141 | +* (6): The latest release of "express" was over 1 year ago |
| 142 | +* (28): The latest release of "mocha" was about 1 year ago |
| 143 | +
|
| 144 | +A few modules are `aging` in terms of the last release. Not necessariliy something to worry about |
| 145 | +yet but worth keeping an eye on (ioredis and kafkajs in particular). |
| 146 | +
|
| 147 | +Aging |
| 148 | +(14): The latest release of "i18next-icu" was about 1 year ago |
| 149 | +(18): The latest release of "ioredis" was about 1 year ago |
| 150 | +(32): The latest release of "odbc" was 11 months ago |
| 151 | +(39): The latest release of "kafkajs" was about 1 year ago |
| 152 | +(53): The latest release of "nyc" was almost 4 years ago |
0 commit comments