ast-metadata-inferer — Greenflagged

[![Test](https://github.com/amilajack/ast-metadata-inferer/actions/workflows/test.yml/badge.svg)](https://github.com/amilajack/ast-metadata-inferer/actions/workflows/test.yml)

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

amilajack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:lib/helpers/AstNodeTypeTester.js	AI (source-diff): File uses nightmare (headless browser) to run JS feature-detection tests via eval() — this is the package's core browser compatibility testing functionality, not malware.	ai	2026/04/24
source-diff	net-exec-file:lib/helpers/ast-node-types-tester.js	AI (source-diff): File uses puppeteer + eval() to run browser compatibility tests — core functionality of this package. Not a dropper/loader; pattern is stable across versions.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is explained by new helper file and large Microsoft API catalog data JSON — legitimate new functionality for this compatibility inference package.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package is 2856 days old with 23 versions — 0.0.0 is the legitimate initial release of a long-standing project, not a throwaway malicious package.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() is used inside a Nightmare.js browser evaluate() callback for browser compatibility testing — a standard and expected pattern for this type of tool.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
0.8.1	1 / 13	2024-12-11
0.8.0	1 / 13	2023-02-09
0.7.0	1 / 13	2021-08-19
0.6.0	1 / 13	2021-08-09
0.5.1	1 / 17	2021-07-18
0.5.0	1 / 17	2021-07-16
0.4.0	0 / 18	2020-06-27
0.2.0	0 / 18	2020-05-24
0.1.1	0 / 15	2019-02-09
0.1.0	0 / 14	2019-02-08
0.0.1	2 / 8	2018-07-06
0.0.0	2 / 8	2018-06-29

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 file with network + code execution: lib/helpers/ast-node-types-tester.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.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.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.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amilajack.

HIGH New file with network + code execution: lib/helpers/ast-node-types-tester.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

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amilajack.

LOW No provenance attestation provenance

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

v0.1.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amilajack.

LOW No provenance attestation provenance

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

v0.0.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amilajack.

HIGH New file with network + code execution: lib/helpers/AstNodeTypeTester.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.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.