@onkernel/create-kernel-app MIT 38 versions

@onkernel/create-kernel-app

npm Repository Homepage

Create Kernel sample applications

38

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

raf-kernelcat-kernel

Keywords

kernelcliscaffoldingautomationplaywrightbrowser-automationtemplates

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:base64-decode	AI (semgrep): Decodes base64 image data for metadata extraction via sharp; no code execution or exfiltration.	ai	2026/05/08
phantom-deps	phantom-dep:ora	AI (phantom-deps): Scaffolding tool; deps referenced in generated templates, not imported by the tool itself.	ai	2026/05/08
phantom-deps	phantom-dep:chalk	AI (phantom-deps): Scaffolding tool; deps referenced in generated templates, not imported by the tool itself.	ai	2026/05/08
phantom-deps	phantom-dep:fs-extra	AI (phantom-deps): Scaffolding tool; deps referenced in generated templates, not imported by the tool itself.	ai	2026/05/08
phantom-deps	phantom-dep:inquirer	AI (phantom-deps): Scaffolding tool; deps referenced in generated templates, not imported by the tool itself.	ai	2026/05/08
phantom-deps	phantom-dep:commander	AI (phantom-deps): Scaffolding tool; deps referenced in generated templates, not imported by the tool itself.	ai	2026/05/08

Versions (showing 38 of 38)

Version	Deps	Published
0.1.40	5 / 9	2025-11-05
0.1.39	5 / 9	2025-10-28
0.1.38	5 / 9	2025-10-21
0.1.37	5 / 9	2025-10-21
0.1.36	5 / 9	2025-10-17
0.1.35	5 / 9	2025-09-30
0.1.34	5 / 9	2025-09-26
0.1.33	5 / 9	2025-09-24
0.1.32	5 / 9	2025-09-12
0.1.31	5 / 9	2025-09-04
0.1.30	5 / 9	2025-08-18
0.1.29	5 / 9	2025-07-22
0.1.28	5 / 9	2025-07-21
0.1.27	5 / 9	2025-07-18
0.1.26	5 / 9	2025-07-14
0.1.25	5 / 9	2025-07-11
0.1.24	5 / 9	2025-07-04
0.1.23	5 / 9	2025-07-03
0.1.22	5 / 9	2025-06-19
0.1.21	5 / 9	2025-06-19
0.1.19	5 / 9	2025-06-16
0.1.18	5 / 9	2025-06-09
0.1.17	5 / 9	2025-06-09
0.1.16	5 / 9	2025-06-08
0.1.15	5 / 9	2025-06-06
0.1.14	5 / 9	2025-06-06
0.1.13	5 / 9	2025-05-29
0.1.12	5 / 9	2025-05-28
0.1.11	5 / 9	2025-05-27
0.1.10	5 / 9	2025-05-23
0.1.9	5 / 9	2025-05-21
0.1.8	5 / 9	2025-05-21
0.1.6	5 / 9	2025-05-19
0.1.4	5 / 9	2025-05-19
0.1.3	5 / 9	2025-05-19
0.1.2	5 / 9	2025-05-19
0.1.1	5 / 9	2025-05-19
0.1.0	5 / 9	2025-05-19

v0.1.40

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

1 finding

LOW No provenance attestation provenance

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

v0.1.38

1 finding

LOW No provenance attestation provenance

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

v0.1.37

1 finding

LOW No provenance attestation provenance

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

v0.1.36

1 finding

LOW No provenance attestation provenance

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

v0.1.35

1 finding

LOW No provenance attestation provenance

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

v0.1.34

1 finding

LOW No provenance attestation provenance

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

v0.1.33

1 finding

LOW No provenance attestation provenance

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

v0.1.32

1 finding

LOW No provenance attestation provenance

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

v0.1.31

1 finding

LOW No provenance attestation provenance

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

v0.1.30

1 finding

LOW No provenance attestation provenance

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

v0.1.29

1 finding

LOW No provenance attestation provenance

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

v0.1.28

1 finding

LOW No provenance attestation provenance

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

v0.1.27

1 finding

LOW No provenance attestation provenance

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

v0.1.26

1 finding

LOW No provenance attestation provenance

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

v0.1.25

1 finding

LOW No provenance attestation provenance

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

v0.1.24

1 finding

LOW No provenance attestation provenance

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

v0.1.23

1 finding

LOW No provenance attestation provenance

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

v0.1.22

1 finding

LOW No provenance attestation provenance

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

v0.1.21

1 finding

LOW No provenance attestation provenance

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

v0.1.19

1 finding

LOW No provenance attestation provenance

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

v0.1.18

1 finding

LOW No provenance attestation provenance

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

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

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

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.