← Home

@tscircuit/eval

npm

Evaluate code in a full tscircuit runtime environment, including Sucrase transpilation and execution, so you just need to send the code to be executed with automatic handling of imports from `@tsci/*`

100
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

seveibar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:@tsci/tscircuit.ti AI (npm-metadata): devDependency, SHA-pinned github ref; build-time only, consistent with prior approved versions. ai
npm-metadata url-dep:@tscircuit/breakout-point-solver AI (npm-metadata): devDependency github ref, not shipped in published package. ai
npm-metadata url-dep:@tscircuit/jlcpcb-manufacturing-specs AI (npm-metadata): SHA-pinned devDependency only; not shipped to consumers, and SHA pinning is actually more secure than semver. ai
source-diff encoded-string-file:dist/webworker/entrypoint.js AI (source-diff): Minified bundled SVG/chart code in webworker entrypoint; not an obfuscated payload, stable pattern for this package. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs a local version-copy script and bun install --ignore-scripts; no external fetch or malicious behavior. ai
source-diff encoded-string-file:dist/blob-url.js AI (source-diff): dist/blob-url.js is intentionally built by build:blob-url script to embed a Web Worker as a base64 blob URL. The encoded content is standard ESM bundler boilerplate, not a malicious payload. Stable pattern for this package. ai

Versions (showing 100 of 996)

Version Deps Published
0.0.1079 0 / 78
0.0.1078 0 / 78
0.0.1077 0 / 78
0.0.1076 0 / 78
0.0.1075 0 / 78
0.0.1074 0 / 78
0.0.1073 0 / 78
0.0.1072 0 / 78
0.0.1071 0 / 78
0.0.1070 0 / 78
0.0.1069 0 / 78
0.0.1068 0 / 78
0.0.1067 0 / 78
0.0.1066 0 / 78
0.0.1065 0 / 78
0.0.1064 0 / 78
0.0.1063 0 / 78
0.0.1062 0 / 78
0.0.1061 0 / 78
0.0.1060 0 / 78
0.0.1059 0 / 78
0.0.1058 0 / 78
0.0.1057 0 / 78
0.0.1056 0 / 78
0.0.1055 0 / 78
0.0.1054 0 / 78
0.0.1053 0 / 78
0.0.1052 0 / 78
0.0.1051 0 / 78
0.0.1050 0 / 77
0.0.1049 0 / 77
0.0.1048 0 / 77
0.0.1047 0 / 77
0.0.1046 0 / 77
0.0.1045 0 / 77
0.0.1044 0 / 77
0.0.1043 0 / 77
0.0.1042 0 / 77
0.0.1041 0 / 77
0.0.1040 0 / 77
0.0.1039 0 / 77
0.0.1038 0 / 77
0.0.1037 0 / 77
0.0.1036 0 / 77
0.0.1035 0 / 77
0.0.1034 0 / 77
0.0.1033 0 / 77
0.0.1032 0 / 77
0.0.1031 0 / 76
0.0.1030 0 / 76
0.0.1029 0 / 76
0.0.1028 0 / 76
0.0.1027 0 / 76
0.0.1026 0 / 76
0.0.1025 0 / 76
0.0.1024 0 / 76
0.0.1023 0 / 76
0.0.1022 0 / 76
0.0.1021 0 / 76
0.0.1020 0 / 76
0.0.1019 0 / 76
0.0.1018 0 / 76
0.0.1017 0 / 76
0.0.1016 0 / 76
0.0.1015 0 / 76
0.0.1014 0 / 76
0.0.1013 0 / 76
0.0.1012 0 / 76
0.0.1011 0 / 76
0.0.1010 0 / 76
0.0.1009 0 / 76
0.0.1008 0 / 76
0.0.1007 0 / 76
0.0.1006 0 / 76
0.0.1005 0 / 76
0.0.1004 0 / 76
0.0.1003 0 / 76
0.0.1002 0 / 76
0.0.1001 0 / 76
0.0.1000 0 / 76
0.0.999 0 / 76
0.0.998 0 / 76
0.0.997 0 / 76
0.0.996 0 / 75
0.0.995 0 / 75
0.0.994 0 / 75
0.0.993 0 / 75
0.0.992 0 / 75
0.0.991 0 / 75
0.0.990 0 / 75
0.0.989 0 / 75
0.0.988 0 / 76
0.0.987 0 / 76
0.0.986 0 / 76
0.0.985 0 / 76
0.0.984 0 / 76
0.0.983 0 / 76
0.0.982 0 / 76
0.0.981 0 / 76
0.0.980 0 / 76
Showing 100 of 996 Next page →

v0.0.1079

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1078

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1077

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1076

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1075

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1074

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1073

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1072

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1071

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1070

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1069

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1068

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1067

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1066

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1065

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1064

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1063

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1062

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1061

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1060

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1059

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1058

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1057

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1056

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1055

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1054

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1053

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1052

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1051

2 findings
HIGH SHA-pinned github dependency (devDependencies): @tsci/tscircuit.ti npm-metadata

Dependency '@tsci/tscircuit.ti' in `devDependencies` points to 'github:tscircuit/ti#57e314be4b2b06bc546d4def7453e619604d1157' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.1050

1 finding
LOW No provenance attestation provenance

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

v0.0.1049

1 finding
LOW No provenance attestation provenance

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

v0.0.1048

1 finding
LOW No provenance attestation provenance

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

v0.0.1047

1 finding
LOW No provenance attestation provenance

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

v0.0.1046

1 finding
LOW No provenance attestation provenance

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

v0.0.1045

1 finding
LOW No provenance attestation provenance

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

v0.0.1044

1 finding
LOW No provenance attestation provenance

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

v0.0.1043

1 finding
LOW No provenance attestation provenance

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

v0.0.1042

1 finding
LOW No provenance attestation provenance

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

v0.0.1041

1 finding
LOW No provenance attestation provenance

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

v0.0.1040

1 finding
LOW No provenance attestation provenance

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

v0.0.1039

1 finding
LOW No provenance attestation provenance

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

v0.0.1038

1 finding
LOW No provenance attestation provenance

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

v0.0.1037

1 finding
LOW No provenance attestation provenance

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

v0.0.1036

1 finding
LOW No provenance attestation provenance

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

v0.0.1035

1 finding
LOW No provenance attestation provenance

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

v0.0.1034

1 finding
LOW No provenance attestation provenance

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

v0.0.1033

1 finding
LOW No provenance attestation provenance

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

v0.0.1032

1 finding
LOW No provenance attestation provenance

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

v0.0.1031

1 finding
LOW No provenance attestation provenance

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

v0.0.1030

1 finding
LOW No provenance attestation provenance

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

v0.0.1029

1 finding
LOW No provenance attestation provenance

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

v0.0.1028

1 finding
LOW No provenance attestation provenance

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

v0.0.1027

1 finding
LOW No provenance attestation provenance

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

v0.0.1026

1 finding
LOW No provenance attestation provenance

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

v0.0.1025

1 finding
LOW No provenance attestation provenance

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

v0.0.1024

1 finding
LOW No provenance attestation provenance

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

v0.0.1023

1 finding
LOW No provenance attestation provenance

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

v0.0.1022

1 finding
LOW No provenance attestation provenance

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

v0.0.1021

1 finding
LOW No provenance attestation provenance

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

v0.0.1020

1 finding
LOW No provenance attestation provenance

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

v0.0.1019

1 finding
LOW No provenance attestation provenance

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

v0.0.1018

1 finding
LOW No provenance attestation provenance

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

v0.0.1017

1 finding
LOW No provenance attestation provenance

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

v0.0.1016

1 finding
LOW No provenance attestation provenance

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

v0.0.1015

1 finding
LOW No provenance attestation provenance

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

v0.0.1014

1 finding
LOW No provenance attestation provenance

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

v0.0.1013

1 finding
LOW No provenance attestation provenance

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

v0.0.1012

1 finding
LOW No provenance attestation provenance

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

v0.0.1011

1 finding
LOW No provenance attestation provenance

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

v0.0.1010

1 finding
LOW No provenance attestation provenance

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

v0.0.1009

1 finding
LOW No provenance attestation provenance

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

v0.0.1008

1 finding
LOW No provenance attestation provenance

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

v0.0.1007

1 finding
LOW No provenance attestation provenance

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

v0.0.1006

1 finding
LOW No provenance attestation provenance

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

v0.0.1005

1 finding
LOW No provenance attestation provenance

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

v0.0.1004

1 finding
LOW No provenance attestation provenance

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

v0.0.1003

1 finding
LOW No provenance attestation provenance

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

v0.0.1002

1 finding
LOW No provenance attestation provenance

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

v0.0.1001

1 finding
LOW No provenance attestation provenance

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

v0.0.1000

1 finding
LOW No provenance attestation provenance

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

v0.0.999

1 finding
LOW No provenance attestation provenance

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

v0.0.998

1 finding
LOW No provenance attestation provenance

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

v0.0.997

1 finding
LOW No provenance attestation provenance

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

v0.0.996

1 finding
LOW No provenance attestation provenance

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

v0.0.995

1 finding
LOW No provenance attestation provenance

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

v0.0.994

1 finding
LOW No provenance attestation provenance

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

v0.0.993

1 finding
LOW No provenance attestation provenance

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

v0.0.992

1 finding
LOW No provenance attestation provenance

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

v0.0.991

1 finding
LOW No provenance attestation provenance

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

v0.0.990

1 finding
LOW No provenance attestation provenance

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

v0.0.989

1 finding
LOW No provenance attestation provenance

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

v0.0.988

1 finding
LOW No provenance attestation provenance

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

v0.0.987

1 finding
LOW No provenance attestation provenance

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

v0.0.986

1 finding
LOW No provenance attestation provenance

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

v0.0.985

1 finding
LOW No provenance attestation provenance

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

v0.0.984

1 finding
LOW No provenance attestation provenance

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

v0.0.983

1 finding
LOW No provenance attestation provenance

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

v0.0.982

1 finding
LOW No provenance attestation provenance

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

v0.0.981

1 finding
LOW No provenance attestation provenance

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

v0.0.980

1 finding
LOW No provenance attestation provenance

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