@skrun-dev/api MIT 6 versions

@skrun-dev/api

npm Repository Homepage

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

skrun-dev

Keywords

skrunagent-skillsai-agents

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	no-description	AI (npm-metadata): Scoped internal package; missing description is a style issue, not a malware indicator.	ai	2026/05/26
phantom-deps	phantom-dep:@hono/node-server	AI (phantom-deps): @hono/node-server is a declared runtime dep used via config/re-export pattern; stable false positive for this package.	ai	2026/05/22
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped package @skrun-dev/api; name reflects its own namespace, not an impersonation of hapi.	ai	2026/04/29
typosquat	typosquat.levenshtein:pg	AI (typosquat): 2-edit distance from pg is coincidental; package is clearly a scoped API framework package.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): 2-edit distance from joi is coincidental; no impersonation intent evident.	ai	2026/04/29
typosquat	typosquat.levenshtein:ajv	AI (typosquat): 2-edit distance from ajv is coincidental; no impersonation intent evident.	ai	2026/04/29

Versions (showing 6 of 6)

Version	Deps	Published
0.8.0	7 / 5	2026-05-22
0.6.0	7 / 5	2026-04-27
0.3.0	5 / 4	2026-04-14
0.2.0	4 / 4	2026-04-12
0.1.1	4 / 4	2026-03-29
0.1.0	4 / 4	2026-03-29

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

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: skrun-dev.

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

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: skrun-dev.

LOW No provenance attestation provenance

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

v0.1.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: skrun-dev.

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.