← Home

@buildeross/zord

npm Repository Homepage
10
Versions
—
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

benedictvsdan13ram

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @buildeross/zord is a design-system package, not a typosquat of zod; name reflects the org and product. ai
typosquat typosquat.levenshtein:cors AI (typosquat): 2-edit distance to cors is coincidental; package is a UI component library under the BuilderOSS org. ai
phantom-deps phantom-dep:@vanilla-extract/css AI (phantom-deps): vanilla-extract/css is used in build config/sprinkles setup; not directly imported in source but legitimately declared. ai
phantom-deps phantom-dep:@vanilla-extract/private AI (phantom-deps): Peer/internal dep of vanilla-extract toolchain; expected in config files, not direct source imports. ai

Versions (showing 10 of 10)

Version Deps Published
0.3.2 8 / 14
0.3.1 8 / 14
0.3.0 8 / 14
0.2.2 8 / 14
0.2.1 8 / 14
0.2.0 8 / 14
0.1.3 9 / 14
0.1.2 9 / 14
0.1.1 9 / 14
0.1.0 9 / 14

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

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

Package name '@buildeross/zord' is 1 edit(s) away from popular package 'zod'.

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

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

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

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

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

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.