← Home

@construct-space/cli

npm

Construct CLI — scaffold, build, develop, and publish spaces

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

construct.space

Keywords

constructclispacegraph

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped CLI package; Levenshtein match to 'joi' is coincidental with no brand/namespace overlap. ai
phantom-deps phantom-dep:ora AI (phantom-deps): Package ships a Bun-compiled bundle; deps are inlined at build time, not imported directly in source. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Same as ora — bundled at build time by Bun. ai
phantom-deps phantom-dep:chokidar AI (phantom-deps): Same as ora — bundled at build time by Bun. ai
phantom-deps phantom-dep:commander AI (phantom-deps): Same as ora — bundled at build time by Bun. ai
phantom-deps phantom-dep:@inquirer/prompts AI (phantom-deps): Same as ora — bundled at build time by Bun. ai

Versions (showing 51 of 51)

Version Deps Published
1.11.0 5 / 5
1.10.1 5 / 5
1.10.0 5 / 5
1.9.6 5 / 5
1.9.5 5 / 5
1.9.4 5 / 2
1.9.3 5 / 2
1.9.2 5 / 2
1.9.1 5 / 2
1.9.0 5 / 2
1.8.1 5 / 2
1.8.0 5 / 2
1.7.7 5 / 2
1.7.6 5 / 2
1.7.5 5 / 2
1.7.4 5 / 2
1.7.3 5 / 2
1.7.2 5 / 2
1.7.1 5 / 2
1.7.0 5 / 2
1.6.6 5 / 2
1.6.5 5 / 2
1.6.4 5 / 2
1.6.3 5 / 2
1.6.2 5 / 2
1.6.0 5 / 2
1.5.1 5 / 2
1.5.0 5 / 2
1.4.5 5 / 2
1.4.4 5 / 2
1.4.3 5 / 2
1.4.2 5 / 2
1.4.1 5 / 2
1.4.0 5 / 2
1.3.1 5 / 2
1.2.0 5 / 2
1.1.12 5 / 2
1.1.11 5 / 2
1.1.9 5 / 2
1.1.8 5 / 2
1.1.6 5 / 2
1.1.4 5 / 2
1.1.3 5 / 2
1.1.2 5 / 2
1.1.0 5 / 2
1.0.7 5 / 2
1.0.6 5 / 2
1.0.5 5 / 2
1.0.4 5 / 2
1.0.2 5 / 2
1.0.0 5 / 2

v1.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.7

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: construct.space.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.