← Home

@windrun-huaiin/backend-core

npm Repository Homepage
41
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

windrun-huaiin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-LLI2WIYN.js AI (source-diff): Bundled @upstash/redis client code; network calls are legitimate Redis HTTP API calls, not malware. ai
source-diff net-exec-file:dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js AI (source-diff): File is bundled @upstash/redis client code; network calls are HTTP to Upstash API, not dropper behavior. ai
source-diff large-new-source-files AI (source-diff): Large file count explained by bundling three Upstash deps into dist/node_modules; stable pattern for this package. ai
phantom-deps phantom-dep:prisma AI (phantom-deps): prisma is a CLI/dev tool referenced in config, not directly imported in source. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() used in a Proxy handler for Upstash client wrapping — idiomatic JS, not obfuscation. ai
phantom-deps phantom-dep:@upstash/lock AI (phantom-deps): @upstash/lock is declared as a dependency and used via config; phantom-dep heuristic is a false positive here. ai

Versions (showing 41 of 41)

Version Deps Published
31.0.1 12 / 7
31.0.0 12 / 7
30.0.0 12 / 7
29.0.3 12 / 7
29.0.2 12 / 7
29.0.1 12 / 7
29.0.0 12 / 7
28.0.1 15 / 7
27.0.0 14 / 7
26.0.2 14 / 7
26.0.1 14 / 7
26.0.0 14 / 7
25.0.1 14 / 7
25.0.0 14 / 7
24.0.0 14 / 7
23.0.0 14 / 7
22.0.0 14 / 7
21.0.0 14 / 7
20.2.0 14 / 7
20.1.0 14 / 7
20.0.1 14 / 7
20.0.0 14 / 7
17.0.0 14 / 7
16.0.0 14 / 7
15.1.0 13 / 7
15.0.0 12 / 7
14.6.0 12 / 7
14.5.0 12 / 7
14.4.0 12 / 7
14.3.0 12 / 7
14.2.0 12 / 7
14.1.1 12 / 7
14.1.0 12 / 7
14.0.0 12 / 7
13.0.0 12 / 7
12.0.0 9 / 7
11.0.3 9 / 7
11.0.2 9 / 7
11.0.1 9 / 7
11.0.0 9 / 7
10.0.1 9 / 6

v31.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v31.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

v27.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

v20.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

v17.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v15.0.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.6.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.5.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.4.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.3.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.1.1

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.1.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-IH7W44G6.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.0

2 findings
HIGH New file with network + code execution: dist/node_modules/.pnpm/@[email protected]/node_modules/@upstash/redis/chunk-LLI2WIYN.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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