localforage — Greenflagged

Offline storage, improved.

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

tofumatt

Keywords

indexeddblocalstoragestoragewebsql

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:site/javascripts/jquery_ui.js	AI (source-diff): Minified jQuery UI v1.10.3 for the project's documentation site; clearly identified by header comment. Standard practice.	ai	2026/04/24
phantom-deps	phantom-dep:express	AI (phantom-deps): Build/dev dependency referenced in config; legitimate pattern for build tools.	ai	2026/04/24
phantom-deps	phantom-dep:coffee-script	AI (phantom-deps): Build/dev dependency referenced in config; legitimate pattern for build tools.	ai	2026/04/24
phantom-deps	phantom-dep:uglify-js	AI (phantom-deps): Build/dev dependency for minification; legitimate pattern for build tools.	ai	2026/04/24
source-diff	obfuscated-file:test/localforage.webpack.js	AI (source-diff): Standard webpack bundle in test directory; webpack bootstrap boilerplate, not obfuscated malicious code. Stable for this package.	ai	2026/04/24
source-diff	obfuscated-file:docs/scripts/flatdoc.js	AI (source-diff): Flatdoc (Rico Sta. Cruz) documentation rendering library in docs/ directory; standard open-source tooling, not obfuscated malware.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): In examples/require.js — bundled RequireJS uses eval for module loading; standard AMD loader pattern.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Gruntfile.js dev tooling using path.resolve for test config; standard build pattern, not a runtime concern.	ai	2026/04/24
source-diff	net-exec-file:docs/scripts/legacy.js	AI (source-diff): HTML5 Shiv + matchMedia polyfill + Respond.js for docs site legacy browser support; well-known OSS libraries.	ai	2026/04/24
source-diff	net-exec-file:docs/scripts/jquery.min.js	AI (source-diff): jQuery v1.9.1 minified in docs/scripts/; standard documentation site asset, not malware.	ai	2026/04/24

Versions (showing 51 of 57)

View all versions

Version	Deps	Published
1.10.0	1 / 38	2021-08-18
1.7.2	1 / 39	2018-06-16
1.7.1	1 / 39	2018-03-30
1.7.0	1 / 39	2018-03-30
1.6.0	1 / 39	2018-03-03
1.5.7	1 / 35	2018-02-23
1.5.6	1 / 35	2018-01-18
1.5.5	1 / 35	2017-11-29
1.5.4	1 / 35	2017-11-28
1.5.3	1 / 35	2017-10-28
1.5.2	1 / 35	2017-10-10
1.5.1	1 / 35	2017-10-08
1.5.0	1 / 35	2017-02-18
1.4.3	1 / 35	2016-10-06
1.4.2	1 / 35	2016-05-15
1.4.1	1 / 35	2016-05-10
1.4.0	1 / 27	2016-02-11
1.3.3	1 / 27	2016-01-27
1.3.2	1 / 27	2016-01-20
1.3.1	1 / 27	2015-12-11
1.3.0	1 / 27	2015-10-09
1.2.10	1 / 22	2015-08-29
1.2.9	1 / 18	2015-08-27
1.2.8	1 / 18	2015-08-24
1.2.7	1 / 18	2015-08-03
1.2.6	1 / 21	2015-08-02
1.2.4	1 / 18	2015-07-06
1.2.3	1 / 17	2015-06-05
1.2.2	1 / 17	2015-02-01
1.2.1	1 / 17	2015-01-06
1.2.0	1 / 17	2014-12-12
1.1.1	1 / 17	2014-10-22
1.1.0	1 / 17	2014-10-19
1.0.4	1 / 17	2014-10-16
1.0.3	1 / 17	2014-10-16
1.0.2	1 / 17	2014-10-09
1.0.1	1 / 17	2014-10-04
1.0.0	1 / 17	2014-10-01
0.9.3	1 / 17	2014-10-01
0.9.2	0 / 17	2014-07-25
0.9.1	0 / 16	2014-07-04
0.9.0	0 / 16	2014-07-03
0.8.1	0 / 12	2014-05-12
0.8.0	0 / 12	2014-05-05
0.7.0	0 / 12	2014-04-25
0.6.2	0 / 11	2014-04-22
0.6.1	0 / 11	2014-04-22
0.6.0	0 / 11	2014-04-22
0.4.3	0 / 11	2014-04-22
0.4.1	0 / 11	2014-04-19
0.4.0	0 / 11	2014-04-11

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.7

1 finding

LOW No provenance attestation provenance

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

v1.5.6

1 finding

LOW No provenance attestation provenance

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

v1.5.5

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

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

LOW No provenance attestation provenance

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

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

4 findings

HIGH New obfuscated file: docs/scripts/flatdoc.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: docs/scripts/jquery.min.js source-diff

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

HIGH New file with network + code execution: docs/scripts/legacy.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.

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.10

1 finding

LOW No provenance attestation provenance

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

v1.2.9

1 finding

LOW No provenance attestation provenance

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

v1.2.8

2 findings

HIGH New obfuscated file: test/localforage.webpack.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.

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

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

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

2 findings

HIGH New obfuscated file: site/javascripts/jquery_ui.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.8.0

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

1 finding

LOW No provenance attestation provenance

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

v0.6.1

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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.