base-methods MIT 23 versions

base-methods

npm Repository Homepage

base-methods is the foundation for creating modular, unit testable and highly pluggable node.js applications, starting with a handful of common methods, like `set`, `get`, `del` and `use`.

23

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

doowbjonschlinkert

Keywords

boilerplatecachedelgetinheritmethodssetstarterunsetvisit

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:set-value	AI (phantom-deps): Lazily required via lazy-cache pattern; static analysis cannot detect runtime require calls. False positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:lazy-cache	AI (phantom-deps): lazy-cache is used to lazily require other deps at runtime — a known pattern in jonschlinkert packages that defeats static import analysis. Not a real phantom dep.	ai	2026/04/24
phantom-deps	phantom-dep:get-value	AI (phantom-deps): Lazily required via lazy-cache pattern; static analysis cannot detect runtime require calls. False positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:collection-visit	AI (phantom-deps): Lazily required via lazy-cache pattern; static analysis cannot detect runtime require calls. False positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:unset-value	AI (phantom-deps): Lazily required via lazy-cache pattern; static analysis cannot detect runtime require calls. False positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:define-property	AI (phantom-deps): Lazily required via lazy-cache pattern; static analysis cannot detect runtime require calls. False positive for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from doowb to jonschlinkert occurred in 2015 and is a documented legitimate transition; jonschlinkert is listed as the package author. Stable for this package.	ai	2026/04/23

Versions (showing 23 of 23)

Version	Deps	Published
0.6.2	9 / 7	2015-12-20
0.6.1	9 / 7	2015-12-02
0.6.0	9 / 7	2015-12-01
0.5.0	9 / 7	2015-11-17
0.4.1	9 / 6	2015-11-08
0.4.0	9 / 7	2015-10-29
0.3.1	8 / 7	2015-10-24
0.3.0	8 / 7	2015-10-22
0.2.14	8 / 7	2015-10-08
0.2.13	8 / 7	2015-10-06
0.2.12	8 / 7	2015-10-06
0.2.11	8 / 7	2015-10-06
0.2.10	8 / 7	2015-10-02
0.2.9	8 / 7	2015-10-01
0.2.8	8 / 7	2015-09-30
0.2.7	8 / 7	2015-09-30
0.2.6	8 / 7	2015-09-15
0.2.5	7 / 2	2015-09-10
0.2.4	7 / 2	2015-09-10
0.2.3	7 / 2	2015-09-08
0.2.2	7 / 2	2015-09-08
0.2.1	6 / 2	2015-08-30
0.2.0	6 / 2	2015-08-29

v0.6.2

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-12-20) provenance

This version was published by a different npm account than previous versions on 2015-12-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.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.5.0

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: jonschlinkert → doowb (on 2015-11-17) provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

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.