@ts-morph/common — Greenflagged

Common functionality for ts-morph packages.

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dsherret

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/typescript.js	AI (source-diff): This file is the bundled Microsoft TypeScript compiler (Apache 2.0 license header visible). @ts-morph/common intentionally bundles TypeScript rather than listing it as a runtime dep — stable pattern for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed from dsherret to GitHub Actions with SLSA provenance — legitimate CI/CD automation transition for this package.	ai	2026/04/24
publish-pattern	dormant-publish	AI (publish-pattern): Mature infrastructure package; long gaps between releases are normal. SLSA provenance confirms legitimate CI/CD publish.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Scoped monorepo sub-package; short README and no keywords are typical for @ts-morph/common.	ai	2026/04/24
source-diff	net-exec-file:dist/data/libFiles.js	AI (source-diff): The 'network' references are TypeScript DOM API type definitions (fetch, XMLHttpRequest interfaces) embedded as text data, not actual network calls. No dynamic code execution present. Stable false positive for this package.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is fully explained by the intentional addition of the 828KB TypeScript lib declarations data bundle (libFiles.js), as evidenced by the new createLibFile build script.	ai	2026/04/24
source-diff	obfuscated-file:dist/data/libFiles.js	AI (source-diff): libFiles.js is a data bundle of TypeScript's built-in declaration files serialized as string literals. Long lines are minified TS type definitions, not obfuscation. This pattern is stable for this package.	ai	2026/04/24

Versions (showing 48 of 48)

Version	Deps	Published
0.29.0	3 / 12	2026-04-12
0.28.1	3 / 12	2025-10-12
0.28.0	3 / 12	2025-09-07
0.27.0	3 / 12	2025-05-19
0.26.1	3 / 12	2025-02-05
0.26.0	3 / 12	2024-12-30
0.25.0	3 / 12	2024-10-06
0.24.0	4 / 12	2024-06-23
0.23.0	4 / 12	2024-03-10
0.22.0	4 / 12	2023-12-02
0.21.0	4 / 14	2023-09-21
0.20.0	4 / 14	2023-06-15
0.19.0	4 / 14	2023-03-28
0.18.1	4 / 13	2022-12-08
0.18.0	4 / 13	2022-11-20
0.17.0	4 / 13	2022-09-03
0.16.0	4 / 13	2022-06-03
0.15.0	4 / 13	2022-05-24
0.13.0	4 / 13	2022-03-03
0.12.3	4 / 13	2022-01-22
0.12.2	4 / 13	2021-11-23
0.12.1	4 / 13	2021-11-22
0.12.0	4 / 13	2021-11-20
0.11.1	4 / 18	2021-10-30
0.11.0	4 / 18	2021-08-27
0.10.1	4 / 18	2021-07-08
0.10.0	4 / 19	2021-05-26
0.9.2	4 / 19	2021-05-15
0.9.1	4 / 19	2021-05-01
0.9.0	3 / 19	2021-03-22
0.8.1	5 / 20	2021-03-06
0.8.0	5 / 20	2021-02-24
0.7.5	6 / 19	2021-02-06
0.7.4	6 / 19	2021-02-06
0.7.3	6 / 19	2021-01-08
0.7.2	6 / 19	2020-11-30
0.7.1	6 / 19	2020-11-26
0.7.0	6 / 19	2020-11-21
0.6.0	6 / 19	2020-08-20
0.5.2	6 / 19	2020-07-20
0.5.1	6 / 19	2020-06-18
0.5.0	6 / 19	2020-05-16
0.4.0	6 / 19	2020-02-23
0.2.2	6 / 19	2019-12-09
0.2.1	6 / 19	2019-12-08
0.2.0	6 / 19	2019-12-07
0.1.1	7 / 20	2019-11-12
0.1.0	7 / 20	2019-11-08

v0.29.0

2 findings

HIGH Publisher changed: dsherret → GitHub Actions (on 2026-04-12) provenance

This version was published by a different npm account than previous versions on 2026-04-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.28.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.28.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.27.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.26.1

1 finding

LOW No provenance attestation provenance

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

v0.26.0

1 finding

LOW No provenance attestation provenance

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

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.2

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

2 findings

HIGH New obfuscated file: dist/typescript.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

3 findings

HIGH New obfuscated file: dist/data/libFiles.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/data/libFiles.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.

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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