---
canonical: "https://firewall.lpm.dev/npm/create-protoyard/v/1.7.0"
markdown: "https://firewall.lpm.dev/npm/create-protoyard/v/1.7.0.md"
package: "create-protoyard"
report_status: "published"
title: "create-protoyard@1.7.0 npm security report"
verdict: "clean"
version: "1.7.0"
---

# create-protoyard@1.7.0 npm security report

> **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document.

## Verdict summary
**Allowed — no malicious behavior detected** — 12 low-signal patterns reviewed and cleared.

- **Verdict:** Clean
- **Product-default install policy:** Allow
- **Firewall policy:** No policy match
- **Public report status:** Published
- **Threat category:** None published
- **Selected version:** 1.7.0
- **Selected version is latest:** No
- **Analysis source:** AI security review (lpm-firewall-ai)

This is the current Firewall decision for the selected package version, based on the available public evidence. Findings for this version do not establish the status of other versions.

AI assessment: clean; recommendation: mark clean. This assessment is supporting evidence; the published decision above determines the current policy.

The source implements an explicit workspace creation CLI: it validates the target and writes scaffold files there, then invokes the Protoyard CLI. The manifest declares no install lifecycle hook, and the review found no unrelated network collection or other attack behavior.

## Latest scan
- **Scanner version:** rust-scanner-worker-schema-1
- **Recorded final verdict:** Clean
- **Recorded analysis confidence:** 95.0%
- **Started:** 2026-11-09T23:51:28.309Z
- **Finished:** 2026-11-09T23:51:56.994Z
- **Download time:** 517 ms
- **Static scan time:** 133 ms
- **AI review time:** 28035 ms
- **Total time:** 28685 ms

The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs.

## Security analysis

### Published attack-surface review

- **Summary:** No attack was identified; the package provides a workspace scaffolding command.

- **Trigger:** The user runs create-protoyard with a target directory.

- **Impact:** Creates the requested project files and may run the chosen package manager’s install command in that new workspace.

- **Review source:** ai\_review

- **Reviewed:** 2026-11-09T23:51:56.994Z

### AI review details

- **Review stage:** source\_first\_review

- **Mechanism:** It creates workspace files in a staging directory, runs Protoyard’s CLI there, and installs dependencies unless installation is skipped.

- **Rationale:** The source implements an explicit workspace creation CLI: it validates the target and writes scaffold files there, then invokes the Protoyard CLI. The manifest declares no install lifecycle hook, and the review found no unrelated network collection or other attack behavior.

- **Files touched:** index.js, bin/create-protoyard.mjs, package.json

### Review decision

- **Verdict:** Clean

- **Confidence:** 95.0%

- **Recommended action:** mark\_clean

- **Intent class:** Benign

- **False-positive risk:** Low

- **Evidence for AI clean decision:** The manifest exposes a library entry and a create-protoyard command, with no install lifecycle hook declared., The CLI invokes main when the user runs the create-protoyard command., Workspace creation validates the requested template and target directory before writing., The package writes scaffold files into a staging directory for the requested workspace, then invokes Protoyard’s CLI to create the starter.

- **Evidence against:** The reviewed source contains no outbound network request or unrelated collector., Environment variables are used to detect the package manager and pass the caller’s environment to the child CLI., The package’s declared npm script is typecheck, not an install hook.

## Affected versions and remediation

This report applies to create-protoyard@1.7.0.

- No action is needed for create-protoyard@1.7.0. Pin the version in your lockfile and check new releases as they are scanned.

## Public findings

These are automated scan signals. The review checked each one and found no malicious behavior, so all of them are cleared.

### 1. Low: Scripts Present (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Manifest
- **Confidence:** 100.0%

Package declares npm scripts.

### 2. Medium: Environment Vars (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Source
- **Confidence:** 75.0%

Package source references environment variables.

### 3. Low: Filesystem (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Source
- **Confidence:** 70.0%

Package source references filesystem APIs.

### 4. High: Sandbox Evasion Gated Capability (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Source
- **Confidence:** 84.0%
- **Path:** index.js
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/index.js>)

Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.

Public source snippet (untrusted):

```javascript
L1: // @ts-check
L2: import { spawnSync } from 'node:child_process';
L3: import {
...
L28: export const VERSION = /** @type {{ version: string }} */ (
L29: JSON.parse(readFileSync(join(HERE, 'package.json'), 'utf8'))
L30: ).version;
...
L53: this.hint = hint;
L54: this.exitCode = EXIT[code];
L55: }
...
L74: /** `pnpm` when the caller ran `pnpm create`, `npm` for `npm create`, else pnpm. */
L75: export function detectPackageManager(userAgent = process.env.npm[redacted] ?? '') {
L76: return userAgent.startsWith('npm/') ? 'npm' : 'pnpm';
```

### 5. Low: High Entropy Strings (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Supply Chain
- **Confidence:** 55.0%

Package source contains high-entropy string patterns.

### 6. Low: Url Strings (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Supply Chain
- **Confidence:** 65.0%

Package source contains URL literals.

### 7. Medium: Structural Risk Force Deep Review (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Artifact Inventory
- **Confidence:** 75.0%

Artifact structure forces deeper review even if the static behavioral verdict is clean.

### 8. High: Known Malware Source Similarity (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Static
- **Confidence:** 97.0%
- **Path:** index.js
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/index.js>)

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

Public source snippet (untrusted):

```javascript
matchType = normalized_sha256
matchedPackage = create-protoyard@1.4.1
matchedPath = index.js
matchedIdentity = npm:Y3JlYXRlLXByb3RveWFyZA:1.4.1
similarity = 1.000
summary = normalized source hash matched finalized malicious source
```

### 9. High: Known Malware Source Fingerprint Signature (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Supply Chain
- **Confidence:** 94.0%
- **Path:** index.js
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/index.js>)

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

Public source snippet (untrusted):

```javascript
matchType = malicious_source_fingerprint_signature
signature = f1e640ed621add6a
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = create-protoyard@1.4.1
matchedPath = index.js
matchedIdentity = npm:Y3JlYXRlLXByb3RveWFyZA:1.4.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
```

### 10. Low: Suspicious Lifecycle Evidence (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Manifest
- **Confidence:** 95.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/package.json>)

The manifest exposes a library entry and a create-protoyard command, with no install lifecycle hook declared.

Public source snippet (untrusted):

```json
"exports": {
    ".": {
      "types": "./index.d.ts",
      "default": "./index.js"
    }
  },
  "bin": {
    "create-protoyard": "./bin/create-protoyard.mjs"
  },
  "files": [
    "LICENSE",
    "bin",
```

### 11. Low: Ai Review Evidence (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Ai Review
- **Confidence:** 95.0%
- **Path:** bin/create-protoyard.mjs
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/bin/create-protoyard.mjs>)

The CLI invokes main when the user runs the create-protoyard command.

Public source snippet (untrusted):

```javascript
#!/usr/bin/env node
// `npm create protoyard <dir>` / `pnpm create protoyard <dir>`.
import { main } from '../index.js';

process.exitCode = await main();
```

### 12. Low: Ai Review Evidence (cleared)
- **Status:** Cleared by review: an automated scan signal, not a confirmed behavior
- **Category:** Ai Review
- **Confidence:** 95.0%
- **Path:** index.js
- **Public source:** [View source](<https://unpkg.com/create-protoyard@1.7.0/index.js>)

Workspace creation validates the requested template and target directory before writing.

Public source snippet (untrusted):

```javascript
export function createWorkspace(options) {
  const cwd = options.cwd ?? process.cwd();
  const template = options.template ?? DEFAULT_TEMPLATE;
  if (!SLUG.test(template)) {
    throw new CreateError(
      'usage',
```

## Dependencies and install lifecycle
- **Lifecycle scripts present:** No

- **Dependencies:** 1
- **Optional dependencies:** 0
- **Peer dependencies:** 0
- **Development dependencies:** 0
- **Published dependency-graph edges:** 1

### Published dependency entries
- protoyard 1.7.0 (Dependency)

## Package metadata
- **Package:** create-protoyard
- **Ecosystem:** npm
- **Version:** 1.7.0
- **License:** MIT
- **Version published:** 2026-11-09T23:50:03.238Z
- **Package first seen:** 2026-10-20T18:38:04.389Z
- **Package last seen:** 2026-11-10T22:16:17.171Z
- **Known versions:** 15
- **Latest version:** 1.9.4
- **Appeal under review:** No
- **Description:** Scaffold a Protoyard workspace with \`npm create protoyard\` or \`pnpm create protoyard\`: pinned protoyard, a workspace marker, AGENTS.md and a starter prototype.
- **Maintainers:** dailybotops
- **Keywords:** protoyard, prototype, create, scaffold
- **Runtime engines:** node: \>=24.20.0
- **Artifact files:** 7
- **Artifact unpacked size:** 30,634 bytes
- **Artifact signatures:** 2
- **Attestations:** Yes
- **Provenance:** https://slsa.dev/provenance/v1

## References
- [HTML security report](<https://firewall.lpm.dev/npm/create-protoyard/v/1.7.0>)
- [Repository](<https://github.com/DailybotHQ/protoyard>)
- [Homepage](<https://protoyard.app/>)
- [Issues](<https://github.com/DailybotHQ/protoyard/issues>)
