sugar — Greenflagged

A Javascript utility library for working with native objects.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

l_andrew_l

Keywords

sugarsugarjsfunctionalbrowserutilityutildatetimepolyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:test/environments/sugar/object.js	AI (source-diff): File is a unit test suite for Sugar's Object methods; no actual network calls or dynamic code execution present. False positive for this test-heavy package.	ai	2026/04/24
source-diff	net-exec-file:unit_tests/environments/underscore/todo/json2.js	AI (source-diff): This is the well-known public domain json2.js polyfill included as a test fixture. The 'network' signal is a URL in a comment; eval() is the classic JSON parsing pattern. No actual network calls or malicious execution.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in test harness allows overriding library path via env var — standard test infrastructure pattern, not a security risk.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Sigstore provenance was not widely adopted at the time of this package's publish; absence is expected for this era and publisher.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Sugar is a long-established package (5366 days) with a clean publisher history. Missing gitHead on a major version bump (1.x→2.x) is consistent with a pipeline change, not a supply chain compromise.	ai	2026/04/24
semgrep	semgrep:new-function-constructor	AI (semgrep): All instances are in unit test files testing that new Function() is recognized as a function type — not dynamic code execution in production code.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() usage is in a bundled json2.js polyfill in unit_tests — a well-known legacy JSON parsing pattern, not production library code.	ai	2026/04/24
semgrep	semgrep:base64-decode	AI (semgrep): Sugar is a utility library; its base64 decode function (Buffer.from(str,'base64').toString('utf8')) is standard, expected functionality with no obfuscation or malicious context.	ai	2026/04/23

Versions (showing 33 of 33)

Version	Deps	Published
2.0.6	1 / 0	2018-12-05
2.0.5	1 / 0	2018-12-05
2.0.4	1 / 0	2016-11-23
2.0.3	1 / 0	2016-11-23
2.0.2	1 / 0	2016-11-05
2.0.1	1 / 0	2016-08-09
2.0.0	1 / 0	2016-07-25
1.5.0	0 / 12	2016-07-25
1.4.1	0 / 0	2013-09-17
1.4.0	0 / 0	2013-08-24
1.3.9	0 / 0	2013-07-29
1.3.8	0 / 0	2013-01-11
1.3.7	0 / 0	2012-11-29
1.3.6	0 / 0	2012-11-02
1.3.5	0 / 0	2012-09-30
1.3.4	0 / 0	2012-09-13
1.3.3	0 / 0	2012-09-12
1.3.2	0 / 0	2012-09-12
1.3.1	0 / 0	2012-09-07
1.3.0	0 / 0	2012-07-26
1.2.5	0 / 0	2012-05-02
1.2.4	0 / 0	2012-03-26
1.2.3	0 / 0	2012-03-07
1.2.2	0 / 0	2012-02-07
1.2.1	0 / 0	2012-01-29
1.2.0	0 / 0	2012-01-19
1.1.3	0 / 0	2011-12-14
1.1.2	0 / 0	2011-12-11
1.1.1	0 / 0	2011-11-15
1.1.0	0 / 0	2011-11-05
1.0.0	0 / 0	2011-10-21
0.9.5	0 / 0	2011-09-05
0.9.4	0 / 0	2011-08-15

v2.0.6

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

LOW No provenance attestation provenance

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

v2.0.5

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

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.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: l_andrew_l.

LOW No provenance attestation provenance

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

v2.0.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: l_andrew_l.

LOW No provenance attestation provenance

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

v1.5.0

1 finding

INFO No provenance attestation provenance

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

v1.4.1

2 findings

HIGH New file with network + code execution: test/environments/sugar/object.js source-diff

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

INFO No provenance attestation provenance

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

v1.4.0

2 findings

HIGH New file with network + code execution: test/environments/sugar/object.js source-diff

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

INFO No provenance attestation provenance

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

v1.3.9

1 finding

INFO No provenance attestation provenance

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

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

v1.3.7

1 finding

INFO No provenance attestation provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

INFO No provenance attestation provenance

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

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

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

v1.3.2

1 finding

INFO No provenance attestation provenance

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

v1.3.1

1 finding

INFO No provenance attestation provenance

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

v1.3.0

1 finding

INFO No provenance attestation provenance

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

v1.2.5

1 finding

INFO No provenance attestation provenance

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

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

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

v1.2.2

1 finding

INFO No provenance attestation provenance

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

v1.2.1

1 finding

INFO No provenance attestation provenance

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

v1.2.0

1 finding

INFO No provenance attestation provenance

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

v1.1.3

2 findings

HIGH New file with network + code execution: unit_tests/environments/underscore/todo/json2.js source-diff

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

INFO No provenance attestation provenance

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

v1.1.2

2 findings

HIGH New file with network + code execution: unit_tests/environments/underscore/todo/json2.js source-diff

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

INFO No provenance attestation provenance

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

v1.1.1

1 finding

INFO No provenance attestation provenance

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

v1.1.0

1 finding

INFO No provenance attestation provenance

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

v1.0.0

1 finding

INFO No provenance attestation provenance

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