Hostile 100% github Download

pleme-io/substrate main

“Opinionated Nix build substrate — the underlying layer that defines how all services and products are built”

AArch64 (ARM64) architecture stringBacktick shell command-substitution syntax

Evidence

Claude Code config directory path settings.local.json · lines 1–8
1{
2 "permissions": {
3 "allow": [
4 "Read(//Users/luis.d/.claude/plans/**)",
5 "Bash(mkdir -p /Users/luis.d/.claude/plans/)"
6 ]
7 }
8}
actions/checkout workflow step reference ai-stack.yml · lines 46–56
46:121… R || 'pleme-private') || 'ubuntu-latest') }}
47 steps:
48 - uses: actions/checkout@v4
49 - uses: pleme-io/actions/hf-hub-upload@main
50 with:
51 repo-id: ${{ inputs.hf-repo }}
52 token: ${{ secrets.HF_TOKEN }}
53 local-path: .
54
55 modal-deploy:
56 if: inputs.modal-e …
Workflow handles environment secrets ai-stack.yml · lines 85–93
85 env:
86 POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }}
87 steps:
88 - if: env.POSTHOG_API_KEY != ''
89 uses: pleme-io/actions/posthog-event@main
90 with:
91 api-key: ${{ secrets.POSTHOG_API_KEY }}
92 project-id: ${{ secrets.POSTHOG_PROJECT_ID }}
93 event: ${{ inputs.posthog-event }}
At least four Markdown-style heading lines testing.md · lines 5–15
5:2… ated. Infrastructure is ONLY instantiated after the full RSpec suite passes.
6
7---
8
9## Three-Layer Test Pyramid
10
11Substrate infrastructure follows a three-layer testing strategy that catches
12errors early and cheaply before touching real cloud resources.
13
14```
15 ┌─────── …
Markdown-style heading precedes a code fence testing.md · lines 157–170
⋯4 lines
161```
162
163### IAM Policy Resource Spec Example
164
165```ruby
⋯5 lines

Showing the top 5 files — 1 more file (37 regions) not shown.

No evidence locations were recorded for this file. Raw result

Keyboard shortcuts on this page: j for the next sample, k for the previous one, x to go back to the feed, d to download the original bytes, r to re-queue the sample for analysis.