← Home

is-valid-app

npm Repository Homepage

Wrapper around is-valid-instance and is-registered for validating `base` plugins. Returns true if `app` is a valid instance of base and a plugin is not registered yet.

6
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

appisvalid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonschlinkert→doowb transition in 2016 is a well-known legitimate handoff within the node-base ecosystem; both are highly trusted npm publishers. ai
maintainer-change maintainer-added AI (maintainer-change): doowb is a long-standing, highly trusted publisher; addition as maintainer in 2016 reflects a legitimate collaboration in the node-base ecosystem. ai

Versions (showing 6 of 6)

Version Deps Published
0.3.0 4 / 3
0.2.1 4 / 3
0.2.0 4 / 3
0.1.2 4 / 3
0.1.1 4 / 3
0.1.0 2 / 3

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

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

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: doowb → jonschlinkert (on 2016-06-27) provenance

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

v0.1.2

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2016-06-21) provenance

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