@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 20.73.0 | 38 / 4 | |
| 20.72.3 | 38 / 4 | |
| 20.72.2 | 38 / 4 | |
| 20.72.1 | 38 / 4 | |
| 20.71.1 | 38 / 4 | |
| 20.71.0 | 38 / 4 | |
| 20.70.0 | 38 / 5 | |
| 20.69.0 | 38 / 5 | |
| 20.68.0 | 38 / 5 | |
| 20.67.0 | 38 / 5 | |
| 20.66.6 | 38 / 5 | |
| 20.66.4 | 38 / 5 | |
| 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 | |
| 20.14.0 | 35 / 6 | |
| 20.13.2 | 35 / 6 | |
| 20.13.0 | 35 / 6 | |
| 20.11.0 | 35 / 6 | |
| 20.10.0 | 35 / 6 | |
| 20.9.0 | 35 / 6 | |
| 20.8.1 | 35 / 6 | |
| 20.6.1 | 35 / 6 | |
| 20.5.0 | 35 / 6 | |
| 20.3.1 | 35 / 6 | |
| 20.2.0 | 35 / 6 | |
| 20.1.0 | 34 / 6 |
v20.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.