recall-os 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -8
- package/dist/cli.js +388 -133
- package/dist/cli.js.map +1 -1
- package/dist/index.js +388 -133
- package/dist/index.js.map +1 -1
- package/examples/generated-flutter/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-flutter/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-generic/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-generic/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-ios-swift/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-ios-swift/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-kotlin-android/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-kotlin-android/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-laravel-api/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-laravel-api/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-laravel-react/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-laravel-react/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-laravel-vue/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-laravel-vue/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-nextjs/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-nextjs/docs/20-security/THREAT_MODEL.md +35 -3
- package/examples/generated-python-fastapi/docs/20-security/SECURITY_MODEL.md +25 -4
- package/examples/generated-python-fastapi/docs/20-security/THREAT_MODEL.md +35 -3
- package/package.json +1 -1
|
@@ -1,11 +1,32 @@
|
|
|
1
1
|
# Security Model
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## Status
|
|
4
4
|
|
|
5
|
-
Draft.
|
|
5
|
+
Draft — fill the prompted sections below with this repository's real model as it grows.
|
|
6
|
+
`recall doctor` flags these as warnings once the repository has real work (a feature, module, or
|
|
7
|
+
accepted decision).
|
|
6
8
|
|
|
7
9
|
## Baseline Rules
|
|
8
10
|
|
|
9
|
-
-
|
|
10
|
-
-
|
|
11
|
+
- Never commit secrets or credentials, and never read or copy `.env` files into docs.
|
|
12
|
+
- Validate and authorize untrusted input at every trust boundary.
|
|
11
13
|
- Do not add network, telemetry, cloud, MCP runtime, or AI API behavior without explicit review.
|
|
14
|
+
|
|
15
|
+
## Authentication And Authorization
|
|
16
|
+
|
|
17
|
+
Describe how this repository authenticates users or clients and how it authorizes actions, including
|
|
18
|
+
where those checks live.
|
|
19
|
+
|
|
20
|
+
## Secrets And Configuration
|
|
21
|
+
|
|
22
|
+
Describe where secrets live, how they are injected, and how configuration is kept out of version
|
|
23
|
+
control.
|
|
24
|
+
|
|
25
|
+
## Sensitive Data
|
|
26
|
+
|
|
27
|
+
Describe the sensitive or personal data this repository handles, and how it is protected at rest and
|
|
28
|
+
in transit.
|
|
29
|
+
|
|
30
|
+
## Dependencies And Supply Chain
|
|
31
|
+
|
|
32
|
+
Describe how third-party dependencies are vetted, pinned, and updated.
|
|
@@ -1,7 +1,39 @@
|
|
|
1
1
|
# Threat Model
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## Status
|
|
4
4
|
|
|
5
|
-
Draft.
|
|
5
|
+
Draft — replace the prompts below with this repository's real analysis as it grows. `recall doctor`
|
|
6
|
+
flags these as warnings once the repository has real work (a feature, module, or accepted decision).
|
|
6
7
|
|
|
7
|
-
|
|
8
|
+
## Assets
|
|
9
|
+
|
|
10
|
+
Describe what this repository must protect: user data, credentials, money, availability, or
|
|
11
|
+
reputation.
|
|
12
|
+
|
|
13
|
+
## Entry Points
|
|
14
|
+
|
|
15
|
+
Describe where untrusted input enters: HTTP endpoints, webhooks, file uploads, queues, CLI input, or
|
|
16
|
+
third-party callbacks.
|
|
17
|
+
|
|
18
|
+
## Trust Boundaries
|
|
19
|
+
|
|
20
|
+
Describe where trust changes: client to server, service to database, your code to third-party APIs.
|
|
21
|
+
|
|
22
|
+
## Threats
|
|
23
|
+
|
|
24
|
+
Describe the concrete threats that apply to this repository, by category:
|
|
25
|
+
|
|
26
|
+
- Spoofing — how identities are faked or sessions stolen.
|
|
27
|
+
- Tampering — how requests, data, or builds are altered (injection, mass assignment).
|
|
28
|
+
- Repudiation — actions that must remain auditable.
|
|
29
|
+
- Information disclosure — how sensitive data or secrets could leak.
|
|
30
|
+
- Denial of service — how the system can be overwhelmed or abused.
|
|
31
|
+
- Elevation of privilege — how a user could gain access they should not have.
|
|
32
|
+
|
|
33
|
+
## Mitigations
|
|
34
|
+
|
|
35
|
+
Describe the control in place or planned for each threat above.
|
|
36
|
+
|
|
37
|
+
## Open Risks
|
|
38
|
+
|
|
39
|
+
Describe accepted or unresolved risks and who owns them.
|