@cleverbrush/env
Type-safe environment variable parsing with @cleverbrush/schema — validated, coerced, structured configs from process.env
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @cleverbrush package in a framework monorepo; Levenshtein match to 'ajv' is coincidental, not impersonation. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 1 / 1 | |
| 4.3.0 | 1 / 1 | |
| 4.2.0 | 1 / 1 | |
| 4.1.0 | 1 / 1 | |
| 4.0.0 | 1 / 1 | |
| 3.1.0 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.