@refinedev/cli
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Intentional env passthrough in CLI script runner; stable pattern for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Encode/decode utility; not a payload obfuscation pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Documented swizzle config loader; stable pattern for this CLI tool. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @refinedev/cli; Levenshtein match to 'joi' is purely incidental. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript compiled packages. | ai | |
| phantom-deps | phantom-dep:node-emoji | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-env-type | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.16.52 | 36 / 23 | |
| 2.16.51 | 36 / 23 | |
| 2.16.46 | 36 / 23 | |
| 2.16.44 | 36 / 23 | |
| 2.16.42 | 36 / 23 | |
| 2.16.40 | 36 / 23 | |
| 2.16.39 | 36 / 23 | |
| 2.16.38 | 37 / 23 | |
| 2.16.37 | 37 / 23 | |
| 2.16.36 | 35 / 22 | |
| 2.16.35 | 35 / 22 | |
| 2.16.34 | 36 / 22 | |
| 2.16.33 | 36 / 22 | |
| 2.16.32 | 36 / 22 |
v2.16.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.