← Home

base-option

npm Repository Homepage

Adds a few options methods to base, like `option`, `enable` and `disable`. See the readme for the full API.

10
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

apiappapplicationbasebase-pluginbasepluginbuilding-blocksconfigconfigurationcreateframeworkoptionoptionspluginpluginssettingstooltoolkittools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonschlinkert is the documented author of the node-base ecosystem; the 2016 transition from doowb is a legitimate maintainer handoff, not a compromise. ai
publish-pattern new-deps-added AI (publish-pattern): All new deps (define-property, get-value, lazy-cache, mixin-deep, set-value) are jonschlinkert's own well-known utilities, consistent with node-base ecosystem refactoring. ai
source-diff source-size-tripled AI (source-diff): Absolute size increase is tiny (~1.2KB); reflects addition of utils.js for lazy-loading new deps, a standard node-base pattern. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.0 8 / 8
0.8.4 8 / 8
0.8.3 8 / 8
0.8.2 8 / 8
0.8.1 8 / 8
0.8.0 8 / 8
0.7.0 6 / 8
0.6.2 6 / 8
0.6.1 2 / 7
0.6.0 2 / 7

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

1 finding
LOW No provenance attestation provenance

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

v0.8.3

1 finding
LOW No provenance attestation provenance

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

v0.8.2

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

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

2 findings
HIGH Publisher changed: doowb → jonschlinkert (on 2016-03-09) provenance

This version was published by a different npm account than previous versions on 2016-03-09. 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.2

2 findings
HIGH Publisher changed: doowb → jonschlinkert (on 2016-03-02) provenance

This version was published by a different npm account than previous versions on 2016-03-02. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.