graphql-tag-pluck — Greenflagged

Pluck graphql-tag template literals

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

ardatandab0mbdotansimhakamilkisielaurigo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Missing gitHead is consistent with the maintainer transition and new publish environment setup. No other indicators of tampering.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from ardatan to dotansimha occurred in 2019; dotansimha is a well-known GraphQL ecosystem maintainer with a strong track record. This is a historical, legitimate transition.	ai	2026/04/24

Versions (showing 27 of 27)

Version	Deps	Published
0.8.7	4 / 25	2019-11-03
0.8.6	4 / 25	2019-10-15
0.8.5	4 / 25	2019-09-22
0.8.4	4 / 25	2019-08-06
0.8.3	4 / 25	2019-07-02
0.8.2	4 / 25	2019-06-18
0.8.1	5 / 24	2019-04-30
0.8.0	5 / 22	2019-03-25
0.7.0	5 / 22	2019-03-07
0.6.0	5 / 22	2019-02-27
0.5.0	5 / 22	2019-01-12
0.4.4	5 / 22	2018-12-19
0.4.3	5 / 22	2018-12-19
0.4.2	5 / 22	2018-12-18
0.4.1	4 / 22	2018-12-17
0.4.0	4 / 22	2018-12-17
0.3.4	4 / 22	2018-12-14
0.3.3	3 / 22	2018-12-11
0.3.2	3 / 22	2018-12-11
0.3.1	3 / 22	2018-12-10
0.3.0	3 / 22	2018-12-10
0.2.4	20 / 12	2018-11-28
0.2.3	20 / 12	2018-11-26
0.2.2	20 / 12	2018-11-23
0.2.1	19 / 12	2018-11-22
0.2.0	19 / 12	2018-11-22
0.1.0	3 / 14	2018-11-21

v0.8.7

1 finding

LOW No provenance attestation provenance

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

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.5

2 findings

HIGH Publisher changed: ardatan → dotansimha (on 2019-09-22) provenance

This version was published by a different npm account than previous versions on 2019-09-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.8.4

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

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

v0.8.3

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: ardatan.

HIGH Publisher changed: dotansimha → ardatan (on 2019-07-02) provenance

This version was published by a different npm account than previous versions on 2019-07-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.8.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dab0mb → dotansimha (on 2019-06-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-18. This could indicate a legitimate maintainer transition or an account compromise.

v0.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dotansimha → dab0mb (on 2019-04-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-30. This could indicate a legitimate maintainer transition or an account compromise.

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

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

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

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.3

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

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