| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 3 | 0% |
| Commands | 0 | 1 | 1 | 0% |
| Section tags | 0 | 0 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 3 only in B- − `minimumReleaseAge` and `minimumReleaseAgeExclude`
- + Agent setup
- + Common tasks
- + Reference
Commands
0 shared · 1 only in A · 1 only in B- − pnpm-workspace.yaml
- + pnpm install
Section tags
0 shared · 0 only in A · 2 only in B- + setup
- + agent-behaviour
Line diff
novuhq/novu · .cursor/rules/pnpm-release-age.mdc
@@ −1 @@
1---
2description: pnpm minimumReleaseAge — never bypass for fresh publishes
3alwaysApply: true
4---
5
6### `minimumReleaseAge` and `minimumReleaseAgeExclude`
7
8Do not add packages to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` to work around the configured `minimumReleaseAge`. That policy applies to every dependency, not only specific names.
9
10If a version was published more recently than `minimumReleaseAge` allows, do not install or bump to it until it is old enough. For urgent security fixes, wait for the window, or resolve to a patched release that already satisfies the age rule—without exempting the package from minimum release age.
11
novuhq/novu · .deepsec/AGENTS.md
@@ +1 @@
1# Agent setup
2
3This is a deepsec scanning workspace. Each registered project has its
4own setup prompt at `data/<id>/SETUP.md` — open the relevant one when
5asked to set a project up.
6
7## Common tasks
8
9- **Set up a project for scanning**: read `data/<id>/SETUP.md` and
10 follow it (read `node_modules/deepsec/SKILL.md`, then fill
11 `data/<id>/INFO.md` from the target codebase).
12- **Add a new project**: run `deepsec init-project <root>` — it
13 scaffolds `data/<id>/` and prints/writes the setup prompt for the
14 new project.
15- **Write a custom matcher** (only after a real true-positive shows you
16 a pattern worth keeping): read
17 `node_modules/deepsec/dist/docs/writing-matchers.md`.
18
19## Reference
20
21The deepsec skill is at `node_modules/deepsec/SKILL.md` (after
22`pnpm install`). The full docs ship at
23`node_modules/deepsec/dist/docs/`.
24
@@ −1 +1 @@
1−---
2−description: pnpm minimumReleaseAge — never bypass for fresh publishes
3−alwaysApply: true
4−---
1+# Agent setup
52
6−### `minimumReleaseAge` and `minimumReleaseAgeExclude`
3+This is a deepsec scanning workspace. Each registered project has its
4+own setup prompt at `data/<id>/SETUP.md` — open the relevant one when
5+asked to set a project up.
76
8−Do not add packages to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` to work around the configured `minimumReleaseAge`. That policy applies to every dependency, not only specific names.
7+## Common tasks
98
10−If a version was published more recently than `minimumReleaseAge` allows, do not install or bump to it until it is old enough. For urgent security fixes, wait for the window, or resolve to a patched release that already satisfies the age rule—without exempting the package from minimum release age.
9+- **Set up a project for scanning**: read `data/<id>/SETUP.md` and
10+ follow it (read `node_modules/deepsec/SKILL.md`, then fill
11+ `data/<id>/INFO.md` from the target codebase).
12+- **Add a new project**: run `deepsec init-project <root>` — it
13+ scaffolds `data/<id>/` and prints/writes the setup prompt for the
14+ new project.
15+- **Write a custom matcher** (only after a real true-positive shows you
16+ a pattern worth keeping): read
17+ `node_modules/deepsec/dist/docs/writing-matchers.md`.
18+
19+## Reference
20+
21+The deepsec skill is at `node_modules/deepsec/SKILL.md` (after
22+`pnpm install`). The full docs ship at
23+`node_modules/deepsec/dist/docs/`.
1124
