这是indexloc提供的服务,不要输入任何密码
Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions readmeForJsmon
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
## Using Jsmon as a Data Source in Subfinder

Jsmon is now available as a subdomain data source in **Subfinder**. To use it, you need a Jsmon API key and a workspace ID.

1. Clone and build Subfinder
```bash
git clone https://github.com/projectdiscovery/subfinder.git
cd subfinder
go build .
2. Get your Jsmon API Key and Workspace ID
Comment on lines +5 to +10
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Close the code fence and fix the build command.

  • The code block opened at Line 6 is never closed, which breaks Markdown rendering for the rest of the document.
  • Building subfinder from the repo root with go build . won’t produce the CLI binary. Build the subfinder command package instead.

Apply this diff:

 ```bash
-    git clone https://github.com/projectdiscovery/subfinder.git
-    cd subfinder
-    go build .
+    git clone https://github.com/projectdiscovery/subfinder.git
+    cd subfinder
+    go build -o subfinder ./v2/cmd/subfinder
+```
🤖 Prompt for AI Agents
In readmeForJsmon around lines 5–10 the Markdown code fence opened before the
git steps is never closed and the build step uses "go build ." which won't
produce the CLI binary; close the triple-backtick after the listed commands and
replace the build step with a build that compiles the subfinder command package
into a subfinder binary (e.g., build the ./v2/cmd/subfinder package and output a
subfinder binary).

Go to https://jsmon.sh/ and create an account.
After logging in, create a workspace.
From the dashboard, open the main menu → Jsmon API → API Keys / Quota.
Copy your API Key.
Note your Workspace ID (available in your workspace settings).
3. Configure Subfinder for Jsmon
The Jsmon configuration format is:
apiKey:wkspId
apiKey → Your Jsmon API Key
wkspId → Your Workspace ID
Edit your Subfinder provider config file (~/.config/subfinder/provider-config.yaml) and add:
jsmon:
- "apiKey:yourWorkspaceId"
Comment on lines +16 to +23
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Correct the configuration format and example.

The current example suggests a literal string "apiKey:yourWorkspaceId", which mixes labels and placeholders. Subfinder provider credentials are typically supplied as a single string with colon-separated values. Clarify placeholders and show a proper YAML snippet.

Apply this diff:

-  The Jsmon configuration format is:
-  apiKey:wkspId
-  apiKey → Your Jsmon API Key
-  wkspId → Your Workspace ID
-  Edit your Subfinder provider config file (~/.config/subfinder/provider-config.yaml) and add:
-  jsmon:
-    - "apiKey:yourWorkspaceId"
+  The Jsmon credential format is:
+  API_KEY:WORKSPACE_ID
+  - API_KEY: your Jsmon API key
+  - WORKSPACE_ID: your workspace ID
+  Edit your Subfinder provider config file (~/.config/subfinder/provider-config.yaml) and add:
+  ```yaml
+  jsmon:
+    - "YOUR_API_KEY:YOUR_WORKSPACE_ID"
+  ```
🤖 Prompt for AI Agents
In readmeForJsmon around lines 16-23, the example mixes labels with
placeholders; update the description to state the format is a single
colon-separated string (apiKey:wkspId) and replace the example entry so the
provider-config.yaml snippet shows a single quoted credential string using
placeholders (e.g. YOUR_API_KEY:YOUR_WORKSPACE_ID), removing the literal
"apiKey:yourWorkspaceId" label mix, and ensure the YAML block is properly
closed.

4. Run Subfinder with Jsmon
Now you can run Subfinder using Jsmon as a source:
subfinder -d <domain> -sources jsmon