Monorepo for the SimplyTweeted project
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
11 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- simply-tweeted-monorepo
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.5s
v2.0.11
9 findings · 7.7s
v0.3.74
10 findings · 2.0s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 3.4s
v0.71.0
142 findings · 0.3s
v2.3.8
148 findings · 7.0s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.8s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged41 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 309 findings across every scanner that examined this package. None of the 11 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 55 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
5 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/release.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
4 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, packages/scheduler/package-lock.json, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, packages/scheduler/package-lock.json, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-r292-9mhp-454m
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
4
55 The review budget for this scan was already spent before these findings were reached.
Rules: CVE-2026-73419, CVE-2026-27121, GHSA-wqjv-9729-c5q2 and 41 more · Files: package-lock.json, /repo/package-lock.json, packages/simply-tweeted-app/package.json and 6 more · reported by trivy, osv-scanner, agent-audit-kit and 1 more
Critical vulnerabilities in dependencies and credential access risk.
This artifact contains multiple critical vulnerabilities in its dependencies, identified in `package-lock.json` files. A high severity finding indicates potential credential access or logging within `packages/scheduler/src/tokenManager.ts`. The presence of numerous high severity findings and components with low analyzability also warrants attention.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Files: package-lock.json, packages/scheduler/package-lock.json, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
3 LOW_ANALYZABILITY
Files: /repo/packages/simply-tweeted-app, /repo/packages/scheduler, /repo · reported by cisco-skill-scanner
2 CVE-2025-58754
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2025-62718
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2025-7783
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-12143
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-23745
Files: package-lock.json · reported by trivy
2 CVE-2026-23950
Files: package-lock.json · reported by trivy
2 CVE-2026-24842
Files: package-lock.json · reported by trivy
2 CVE-2026-25639
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-26960
Files: package-lock.json · reported by trivy
2 CVE-2026-29786
Files: package-lock.json · reported by trivy
2 CVE-2026-31802
Files: package-lock.json · reported by trivy
2 CVE-2026-40175
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42033
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42034
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42035
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42036
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42037
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42038
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42039
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42041
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42042
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42043
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42044
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42264
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-42338
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44486
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44487
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44488
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44490
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44494
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44495
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-44496
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 CVE-2026-53655
Files: package-lock.json · reported by trivy
2 CVE-2026-59871
Files: package-lock.json · reported by trivy
2 CVE-2026-59873
Files: package-lock.json · reported by trivy
2 CVE-2026-59874
Files: package-lock.json · reported by trivy
2 CVE-2026-59875
Files: package-lock.json · reported by trivy
2 CVE-2026-69192
Files: package-lock.json, packages/scheduler/package-lock.json · reported by trivy
2 GHSA-23hp-3jrh-7fpw
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-34x7-hfp2-rc4v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-3g43-6gmg-66jw
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-43fc-jf86-j433
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-4hjh-wcwx-xvwj
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-83g3-92jg-28cx
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-866w-xmhq-wj7x
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-8qq5-rm4j-mr97
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-8x88-c5mf-7j5w
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-9ppj-qmqm-q256
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-fjxv-7rqg-78g4
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-gvwx-54wh-qm9j
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-mwp4-54f8-5fhr
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-q8qp-cvcw-x6jj
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-qffp-2rhf-9h96
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r6q2-hw4h-h46w
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-v2v4-37r5-5v8g
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-vmf3-w455-68vh
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w8wr-v893-vjvp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
2 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json, /repo/packages/scheduler/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-001
Files: packages/scheduler/package.json · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: packages/scheduler/src/tokenManager.ts · reported by agent-audit-kit
1 CVE-2025-57820
Files: package-lock.json · reported by trivy
1 CVE-2025-64756
Files: package-lock.json · reported by trivy
1 CVE-2025-67647
Files: package-lock.json · reported by trivy
1 CVE-2026-13149
Files: package-lock.json · reported by trivy
1 CVE-2026-14257
Files: package-lock.json · reported by trivy
1 CVE-2026-22775
Files: package-lock.json · reported by trivy
1 CVE-2026-26996
Files: package-lock.json · reported by trivy
1 CVE-2026-27606
Files: package-lock.json · reported by trivy
1 CVE-2026-27901
Files: package-lock.json · reported by trivy
1 CVE-2026-27903
Files: package-lock.json · reported by trivy
1 CVE-2026-27904
Files: package-lock.json · reported by trivy
1 CVE-2026-30226
Files: package-lock.json · reported by trivy
1 CVE-2026-33671
Files: package-lock.json · reported by trivy
1 CVE-2026-33672
Files: package-lock.json · reported by trivy
1 CVE-2026-39363
Files: package-lock.json · reported by trivy
1 CVE-2026-39365
Files: package-lock.json · reported by trivy
1 CVE-2026-40073
Files: package-lock.json · reported by trivy
1 CVE-2026-40074
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-42573
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-48815
Files: package-lock.json · reported by trivy
1 CVE-2026-53571
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-69152
Files: package-lock.json · reported by trivy
1 CVE-2026-73418
Files: package-lock.json · reported by trivy
1 CVE-2026-73420
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-29g2-3rmr-qm68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2crg-3p73-43xp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52v5-jr5w-gjxr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7rqj-j65f-68wh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g2pg-6438-jwpf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j62c-4x62-9r35
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m56q-vw4c-c2cp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pr6f-5x2q-rwfp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vj54-72f3-p5jv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqjv-9729-c5q2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xmf8-cvqr-rfgj
Files: /repo/package-lock.json · reported by osv-scanner
Showing 25 of 25; the rest are in the per-scanner reports above.