salesprompter-cli 0.1.27 → 0.1.29

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,35 @@
+# Code of Conduct
+
+## Our standard
+
+We expect contributors and maintainers to keep this project respectful, direct, and constructive.
+
+Examples of expected behavior:
+
+- assume good intent
+- focus feedback on the code and product behavior
+- use factual, reproducible reports
+- be respectful in disagreement
+- help keep the project usable for others
+
+Examples of unacceptable behavior:
+
+- harassment or personal attacks
+- discriminatory language
+- doxxing or publishing private information
+- bad-faith disruption
+- spam, abuse, or intimidation
+
+## Enforcement
+
+Project maintainers may remove, edit, or reject comments, commits, issues, or pull requests that violate this code of conduct.
+
+Repeated or severe violations may result in temporary or permanent exclusion from project spaces.
+
+## Reporting
+
+To report conduct issues, contact:
+
+- `hello@danielsinewe.com`
+
+Please include links, screenshots, or other concrete context where possible.

package/CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing to salesprompter-cli
+
+Thanks for contributing to `salesprompter-cli`.
+
+## Scope
+
+This repository contains the public CLI for Salesprompter:
+
+- guided setup and auth flows
+- lead-generation and enrichment commands
+- docs-site source for the CLI docs experience
+- tests for command contracts and user-facing behavior
+
+## Development setup
+
+Requirements:
+
+- Node.js `>=20`
+- npm
+
+Install dependencies:
+
+```bash
+npm install
+```
+
+Build the CLI:
+
+```bash
+npm run build
+```
+
+Run the main verification steps:
+
+```bash
+npm test
+```
+
+For broader repo checks:
+
+```bash
+npm run verify:all
+```
+
+## Change guidelines
+
+Please keep changes aligned with the product-facing CLI surface:
+
+- prefer stable, user-facing command names over internal implementation names
+- keep default help and README examples concise and product-oriented
+- add or update tests when command behavior, payloads, or parsing rules change
+- avoid introducing hidden infrastructure details into normal CLI output
+
+## Pull requests
+
+Before opening a PR:
+
+1. Run `npm run build`
+2. Run `npm test`
+3. Update docs or README when user-facing behavior changes
+4. Keep PRs focused on one logical change when possible
+
+PR descriptions should include:
+
+- what changed
+- why it changed
+- how it was verified
+- any follow-up work or known limits
+
+Use the PR template in `.github/pull_request_template.md`.
+
+## Reporting bugs
+
+When reporting a bug, include:
+
+- the command you ran
+- the input shape or sample payload
+- expected behavior
+- actual behavior
+- relevant JSON output or error messages
+- your environment details such as Node version and OS
+
+## Security
+
+Do not open public issues for security-sensitive findings. Use the process in [SECURITY.md](./SECURITY.md).
+
+## Releases
+
+For release steps, see [RELEASING.md](./RELEASING.md).

package/README.md

@@ -1,6 +1,8 @@
 # salesprompter-cli
 
-Salesprompter CLI helps you go from company or product input to qualified leads with a guided terminal flow.
+Salesprompter CLI is a terminal workflow for lead generation, enrichment, scoring, and sync.
+
+It helps operators and agents go from company, market, or product input to qualified outbound-ready leads with a product-facing command surface and machine-readable output.
 
 ## Install
 
@@ -34,6 +36,15 @@ New here? Create your account at `https://salesprompter.ai/sign-up`, then run `s
 
 For headless or automation use, generate a CLI token in the app and run `salesprompter auth:login --token <token>`.
 
+## What it does
+
+- guided setup and auth
+- product and market discovery
+- Sales Navigator search orchestration
+- contact and company enrichment
+- email-enrichment batch preparation
+- scored-lead sync into downstream systems
+
 ## Common commands
 
 ```bash
@@ -46,6 +57,9 @@ salesprompter --json auth:whoami
 # Resolve profile URLs for a pasted contact list
 salesprompter contacts:find-linkedin-urls --in ./contacts.tsv --out ./contacts.enriched.json
 
+# Resolve LinkedIn company URLs for a pasted company list
+salesprompter companies:resolve-linkedin-urls --in ./companies.txt --out ./companies.enriched.json
+
 # Build and start email enrichment from pasted company/contact rows
 # When authenticated, Salesprompter first enriches company domains in the app, then the CLI builds the email batch.
 salesprompter contacts:resolve-emails --in ./contacts.tsv --out-dir ./email-run --dry-run
@@ -67,6 +81,21 @@ salesprompter --help
 - Use your own authorized data access and workspace credentials.
 - Respect provider terms and customer data boundaries.
 - The CLI is designed for interactive users and agent-assisted workflows.
+- A repo-local Chrome extension compatibility copy is available in `chrome-extension/` for local LinkedIn session sync and popup copy/debug flows.
+
+## Development
+
+```bash
+npm install
+npm run build
+npm test
+```
+
+For contribution and security processes, see:
+
+- [CONTRIBUTING.md](./CONTRIBUTING.md)
+- [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md)
+- [SECURITY.md](./SECURITY.md)
 
 ## Links
 

package/SECURITY.md

@@ -0,0 +1,35 @@
+# Security Policy
+
+## Supported versions
+
+Security fixes are applied to the latest published CLI version.
+
+If you are reporting a vulnerability, please verify it against the latest release first when possible.
+
+## Reporting a vulnerability
+
+Please do not report security vulnerabilities through public GitHub issues.
+
+Send reports to:
+
+- `hello@danielsinewe.com`
+
+Include:
+
+- affected version
+- reproduction steps
+- impact assessment
+- logs, screenshots, or proof of concept if available
+
+## Response expectations
+
+We aim to:
+
+- acknowledge receipt promptly
+- reproduce and assess the report
+- ship a fix or mitigation when confirmed
+- coordinate disclosure when appropriate
+
+## Sensitive data
+
+This CLI may operate on customer lead data, workspace metadata, and authenticated sessions. Please avoid sending real customer data unless it is necessary to reproduce the issue.