@hg-storefront/gift — Greenflagged

A collection of React hooks and plugin configuration for managing gift functionality in the Hemglass storefront.

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

haustech

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:index-VB1hK3Ew.mjs	AI (source-diff): Same bundle as CJS counterpart; same rationale.	ai	2026/05/12
source-diff	obfuscated-file:browser-ponyfill-DhRrEg23-CAvYPDXg.js	AI (source-diff): Fetch polyfill chunk from bundler; recognizable OSS code, not obfuscated malware.	ai	2026/05/12
source-diff	obfuscated-file:browser-ponyfill-DSfu_D2S-VYSU-KPM.js	AI (source-diff): Duplicate fetch polyfill chunk; same rationale as above.	ai	2026/05/12
source-diff	net-exec-file:index-CgU7xgEY.js	AI (source-diff): Network calls are fetch API usage in a storefront component; dynamic code is React internals, not a dropper.	ai	2026/05/12
source-diff	obfuscated-file:index-CgU7xgEY.js	AI (source-diff): Standard Vite/Rollup bundle containing React and OSS libraries; minification is expected for this package.	ai	2026/05/12
source-diff	obfuscated-file:index-VB1hK3Ew.mjs	AI (source-diff): ESM build artifact of the same bundle; minification expected.	ai	2026/05/12
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Fires on bundled axios/graphql client code; not malicious obfuscation, stable pattern for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@hg-storefront/types	AI (phantom-deps): Same-org types package; phantom-dep false positive for type-only dependencies.	ai	2026/04/30
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped package @hg-storefront/gift; the 'gift' name is clearly domain-specific, not a typosquat of 'got'.	ai	2026/04/30

Versions (showing 29 of 29)

Version	Deps	Published
1.0.2	1 / 0	2026-05-19
1.0.1	1 / 0	2026-05-11
1.0.0	1 / 0	2026-05-05
0.0.33	1 / 0	2026-05-04
0.0.30	1 / 0	2026-03-26
0.0.29	1 / 0	2025-12-17
0.0.28	1 / 0	2025-12-16
0.0.27	1 / 0	2025-11-27
0.0.26	1 / 0	2025-11-17
0.0.25	1 / 0	2025-11-14
0.0.24	1 / 0	2025-11-14
0.0.23	1 / 0	2025-11-14
0.0.22	1 / 0	2025-11-14
0.0.21	1 / 0	2025-11-12
0.0.20	1 / 0	2025-11-12
0.0.19	1 / 0	2025-11-11
0.0.17	1 / 0	2025-10-27
0.0.16	1 / 0	2025-10-16
0.0.15	1 / 0	2025-10-13
0.0.14	1 / 0	2025-10-08
0.0.13	1 / 0	2025-10-08
0.0.12	1 / 0	2025-10-07
0.0.11	1 / 0	2025-10-02
0.0.10	1 / 0	2025-09-26
0.0.9	1 / 0	2025-09-25
0.0.8	1 / 0	2025-09-18
0.0.6	1 / 0	2025-09-05
0.0.5	1 / 0	2025-08-14
0.0.4	1 / 0	2025-08-14

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.29

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.26

1 finding

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

7 findings

HIGH New obfuscated file: browser-ponyfill-DhRrEg23-CAvYPDXg.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 obfuscated file: browser-ponyfill-DSfu_D2S-VYSU-KPM.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 obfuscated file: index-CgU7xgEY.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: index-CgU7xgEY.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: index-VB1hK3Ew.mjs 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: index-VB1hK3Ew.mjs 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.6

1 finding

LOW No provenance attestation provenance

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

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

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.