← Home

@coast/schemas

npm Repository Homepage

1. Major - Breaking changes (incompatible schemas) 2. Minor - new blocks, new templates 3. Patch - block iteration

2
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

russelltagazakcoastcoast-botreid-coast

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Fires only in a dev-time codegen script, not in published runtime code. ai

Versions (showing 2 of 2)

Version Deps Published
4.0.2 1 / 19
4.0.0 1 / 19

v4.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.