← Home

@slowcook-ai/mock-runtime

npm Repository Homepage

Runtime for slowcook's per-consumer UI mock app — Scenario types, registry, React hooks, ScenarioPicker UI. Imported by the mock/ scaffolding `slowcook init mock` writes. The mock is the design contract: vibe + plate evolve it; brew copies its components

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

aminazar

Keywords

slowcookmockuiscenariosdesign-contractreactnext

Versions (showing 8 of 8)

Version Deps Published
0.3.4 1 / 5
0.3.3 1 / 4
0.3.2 1 / 4
0.3.1 1 / 4
0.3.0 1 / 4
0.2.0 1 / 4
0.1.1 1 / 4
0.1.0 0 / 4

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.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.