idb-wrapper MIT 21 versions

idb-wrapper

npm Repository Homepage

A cross-browser wrapper for IndexedDB

21

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

raynosjensarps

Keywords

storageofflineIndexedDB

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change (raynos→jensarps) occurred in 2012 and reflects the original author (jensarps) taking over publishing; package.json and GitHub repo both confirm jensarps as canonical owner.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): jensarps is the original author per package.json and GitHub repo; this 2012 maintainer addition is a legitimate ownership transition, not a compromise.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() usage is in example/lib/requirejs/require.js — a bundled copy of RequireJS's documented req.exec() for dynamic module loading, not in the package's main runtime code. Stable false positive for this package.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
1.7.2	0 / 15	2017-11-28
1.7.1	0 / 15	2016-08-31
1.7.0	0 / 14	2016-04-01
1.6.2	0 / 14	2016-03-02
1.6.1	0 / 2	2015-11-07
1.6.0	0 / 2	2015-10-09
1.5.0	0 / 2	2015-04-23
1.4.1	0 / 2	2013-11-11
1.4.0	0 / 0	2013-09-24
1.3.0	0 / 0	2013-08-29
1.2.0	0 / 0	2013-05-31
1.1.0	0 / 0	2013-03-26
1.0.0	0 / 0	2013-02-05
0.3.1	0 / 0	2013-01-04
0.3.0	0 / 0	2012-12-18
0.2.1	0 / 0	2012-11-20
0.1.4	0 / 0	2012-11-18
0.1.3	0 / 0	2012-11-17
0.1.2	0 / 0	2012-11-17
0.1.1	0 / 0	2012-11-17
0.1.0	0 / 0	2012-11-17

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

1 finding

LOW No provenance attestation provenance

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

v1.6.1

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

1 finding

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

2 findings

HIGH Publisher changed: raynos → jensarps (on 2012-11-20) provenance

This version was published by a different npm account than previous versions on 2012-11-20. 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.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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.