← Home

@alloy-js/go

Go bindings for Alloy

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

bterlson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:got AI (typosquat): Scoped @alloy-js/go is a Go-language binding for the Alloy framework, not a typosquat of 'got'. ai
typosquat typosquat.levenshtein:glob AI (typosquat): Same scoped package; Levenshtein match to 'glob' is coincidental. ai
typosquat typosquat.levenshtein:koa AI (typosquat): Same scoped package; Levenshtein match to 'koa' is coincidental. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same scoped package; Levenshtein match to 'pg' is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Same scoped package; Levenshtein match to 'qs' is coincidental. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Same scoped package; Levenshtein match to 'joi' is coincidental. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Same scoped package; Levenshtein match to 'zod' is coincidental. ai
phantom-deps phantom-dep:change-case AI (phantom-deps): change-case is a declared runtime dependency; phantom-dep heuristic false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.0 3 / 7
0.2.0 3 / 7
0.1.0 3 / 7
0.0.1 3 / 7

v0.3.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'got' typosquat

Package name '@alloy-js/go' is 1 edit(s) away from popular package 'got'.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

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.

v0.0.1

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.