← Home

@kopexa/krn

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

julian.kpxsteffen.kopexa

Keywords

krnkopexaresource-namesgrccomplianceframeworks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is the org's initial release convention; package is a legitimate scoped utility with a real repo. ai
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @kopexa package; name similarity to koa is coincidental, unrelated domain (GRC resource names). ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 0 / 5
1.0.1 0 / 5
1.0.0 0 / 5
0.0.0 0 / 5

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

v1.0.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.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.