@wessberg/ts-evaluator — Greenflagged

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

wessberg

Keywords

typescripttsinterpreterevaluateevaluatorast

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall runs 'npm run build' (rollup bundler) to compile TypeScript source. Transparent, no remote code execution. Common pattern for this era of TypeScript packages from this publisher.	ai	2026/04/24
phantom-deps	phantom-dep:@types/find-up	AI (phantom-deps): @types/* packages are type definitions loaded by convention in TypeScript projects; not a security concern.	ai	2026/04/24
phantom-deps	phantom-dep:@types/deasync	AI (phantom-deps): @types/deasync accompanies the deasync runtime dependency; standard TypeScript types pattern.	ai	2026/04/24
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a standard TypeScript type dependency shipped as a runtime dep for type consumers; not a true phantom dependency for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates npm Sigstore provenance by years; absence is expected and not a risk signal for this established package.	ai	2026/04/24
phantom-deps	phantom-dep:@types/object-path	AI (phantom-deps): @types/object-path accompanies the object-path runtime dependency; standard TypeScript types pattern.	ai	2026/04/24
phantom-deps	phantom-dep:@types/jsdom	AI (phantom-deps): @types/jsdom is an optional type dependency for jsdom integration; standard pattern for TypeScript libraries.	ai	2026/04/24

Versions (showing 28 of 28)

Version	Deps	Published
0.0.29	4 / 40	2021-05-17
0.0.28	4 / 39	2021-03-17
0.0.27	4 / 38	2020-10-20
0.0.26	4 / 37	2020-08-07
0.0.25	7 / 22	2020-03-01
0.0.24	9 / 14	2019-11-09
0.0.23	10 / 13	2019-10-14
0.0.22	10 / 13	2019-09-09
0.0.21	10 / 11	2019-05-29
0.0.20	11 / 11	2019-04-25
0.0.19	11 / 11	2019-03-06
0.0.18	10 / 7	2018-12-30
0.0.17	10 / 7	2018-12-30
0.0.16	10 / 7	2018-12-30
0.0.15	10 / 7	2018-12-30
0.0.14	10 / 7	2018-12-30
0.0.13	10 / 7	2018-12-29
0.0.12	10 / 7	2018-12-29
0.0.11	10 / 7	2018-12-28
0.0.10	10 / 7	2018-12-28
0.0.9	10 / 7	2018-12-19
0.0.8	10 / 7	2018-12-18
0.0.7	10 / 7	2018-12-16
0.0.6	10 / 7	2018-12-16
0.0.5	10 / 7	2018-12-16
0.0.4	10 / 7	2018-12-16
0.0.3	10 / 7	2018-12-16
0.0.2	10 / 7	2018-12-16

v0.0.29

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.

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

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.

v0.0.26

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.

v0.0.25

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.

v0.0.24

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.

v0.0.23

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.

v0.0.22

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.

v0.0.21

1 finding

INFO No provenance attestation provenance

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

v0.0.20

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.

v0.0.19

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.

v0.0.18

1 finding

INFO No provenance attestation provenance

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

v0.0.17

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.

v0.0.16

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.

v0.0.15

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.

v0.0.14

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.

v0.0.13

1 finding

INFO No provenance attestation provenance

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

v0.0.12

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.

v0.0.11

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.

v0.0.10

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.

v0.0.9

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.

v0.0.8

1 finding

INFO No provenance attestation provenance

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

v0.0.7

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.

v0.0.6

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.

v0.0.5

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.

v0.0.4

1 finding

INFO No provenance attestation provenance

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

v0.0.3

1 finding

INFO No provenance attestation provenance

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

v0.0.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: npm run build

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.