← Home

@alwatr/on

npm Repository Homepage
5
Versions
—
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

alimd

Keywords

actionalwatrbrowser-apideclarative-uidecoratordirectivedomesmeventfrontendjavascriptlightweightmodulenanolibsignalspatypescriptui-libraryvanilla-jsweb-development

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @alwatr package; Levenshtein match on short name 'on' is a false positive. ai

Versions (showing 5 of 5)

Version Deps Published
9.11.1 2 / 5
9.11.0 2 / 5
9.10.1 2 / 5
9.10.0 2 / 5
9.9.0 2 / 5

v9.11.1

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.

v9.11.0

1 finding
LOW No provenance attestation provenance

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

v9.10.1

1 finding
LOW No provenance attestation provenance

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

v9.10.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.

v9.9.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.