@uniformdev/cli
Uniform command line interface tool
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:normalize-newline | AI (dependencies): Stable utility dep used across many @uniformdev versions; no malicious history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped enterprise CLI package; sparse README and no keywords are typical for this org's packages. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared runtime dep used transitively via graphql-request; phantom-dep heuristic fires but it's a real dependency. | ai | |
| phantom-deps | phantom-dep:call-bind | AI (phantom-deps): call-bind is a transitive utility dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @uniformdev/cli cannot plausibly be a typosquat of 'joi'; Levenshtein match is spurious. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 20.66.2 | 38 / 5 | |
| 20.66.1 | 38 / 5 | |
| 20.66.0 | 38 / 5 | |
| 20.65.0 | 38 / 5 | |
| 20.64.0 | 38 / 5 | |
| 20.63.0 | 38 / 5 | |
| 20.61.1 | 38 / 5 | |
| 20.60.2 | 38 / 5 | |
| 20.60.0 | 38 / 5 | |
| 20.58.0 | 38 / 5 | |
| 20.57.1 | 38 / 5 | |
| 20.56.0 | 38 / 5 | |
| 20.45.0 | 38 / 5 | |
| 20.43.1 | 38 / 5 | |
| 20.43.0 | 38 / 5 | |
| 20.42.1 | 38 / 6 | |
| 20.42.0 | 38 / 6 | |
| 20.41.0 | 38 / 6 | |
| 20.24.0 | 35 / 6 | |
| 20.23.0 | 35 / 6 | |
| 20.20.3 | 35 / 6 | |
| 20.20.0 | 35 / 6 | |
| 20.18.0 | 35 / 6 | |
| 20.16.0 | 35 / 6 | |
| 20.15.0 | 35 / 6 | |
| 20.14.2 | 35 / 6 | |
| 20.14.1 | 35 / 6 |
v20.66.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.