@dawn-ai/cli
The `dawn` command-line interface for validating Dawn apps, inspecting routes, and generating route types.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change to GitHub Actions CI publisher is a benign automation transition for this package. | ai | |
| dependencies | unvetted-dep:@dawn-ai/sqlite-storage | AI (dependencies): First-party same-org monorepo dep. | ai | |
| dependencies | unvetted-dep:@dawn-ai/permissions | AI (dependencies): First-party same-org monorepo dep. | ai | |
| provenance | regressed-provenance | AI (provenance): Manual publish by known maintainer blove on prior versions; not a compromise for this package. | ai | |
| dependencies | unvetted-dep:@dawn-ai/ag-ui | AI (dependencies): Same-org sibling package published in lockstep with this version. | ai | |
| bogus-package | bogus-package | AI (bogus-package): CLI tool in a monorepo org scope; sparse README and no keywords are expected for internal/early-stage tooling. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes via CI/CD with Sigstore attestation; strong supply chain integrity signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org sibling package pinned to the same version; not a third-party injection risk. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @dawn-ai/cli vs unscoped 'joi' — different namespace, no plausible impersonation intent. | ai | |
| phantom-deps | phantom-dep:@dawn-ai/langgraph | AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a runtime dep used in config/scripts, not directly imported in source; stable false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.8.11 | 10 / 7 | |
| 0.8.10 | 8 / 7 | |
| 0.8.9 | 8 / 7 | |
| 0.8.8 | 8 / 7 | |
| 0.8.7 | 8 / 7 | |
| 0.8.6 | 8 / 7 | |
| 0.8.5 | 8 / 6 | |
| 0.8.4 | 8 / 6 | |
| 0.8.3 | 8 / 6 | |
| 0.8.2 | 7 / 6 | |
| 0.8.1 | 7 / 6 | |
| 0.8.0 | 7 / 6 | |
| 0.7.0 | 7 / 6 | |
| 0.6.0 | 7 / 6 | |
| 0.5.0 | 7 / 6 | |
| 0.4.0 | 7 / 6 | |
| 0.3.0 | 7 / 6 | |
| 0.2.0 | 7 / 6 | |
| 0.1.8 | 5 / 4 | |
| 0.1.7 | 5 / 4 | |
| 0.1.6 | 5 / 4 | |
| 0.1.5 | 5 / 4 | |
| 0.1.4 | 5 / 4 | |
| 0.1.3 | 5 / 4 | |
| 0.1.2 | 5 / 4 | |
| 0.1.1 | 5 / 4 | |
| 0.1.0 | 5 / 4 | |
| 0.0.2 | 5 / 4 |
v0.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
3 findingsThis version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.