@inkeep/agents-ui-js Inkeep, Inc. Customer License (IICL) v1.1 41 versions

@inkeep/agents-ui-js

npm Repository Homepage

To run:

41

Versions

Inkeep, Inc. Customer License (IICL) v1.1

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

abraham-inkeepnick-inkeeprobert-inkeepsarah-inkeepvarun-inkeepandrew-inkeepomar-inkeepmiles-inkeep

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:react	AI (phantom-deps): Bundled embed package; React is bundled into dist rather than directly imported in source.	ai	2026/05/14
phantom-deps	phantom-dep:@inkeep/cxkit-react	AI (phantom-deps): Same-org dependency bundled into dist; phantom detection is a false positive for this build pattern.	ai	2026/05/14
provenance	publisher-changed	AI (provenance): Transition from human publisher to GitHub Actions CI/CD is expected for this org; stable pattern going forward.	ai	2026/05/08
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Declared in dependencies; used in build/config context.	ai	2026/05/05
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Declared in dependencies; used in build/config context.	ai	2026/05/05
phantom-deps	phantom-dep:merge-anything	AI (phantom-deps): Declared in dependencies; used in build/config context.	ai	2026/05/05

Versions (showing 41 of 41)

Version	Deps	Published
0.17.1	4 / 16	2026-06-05
0.17.0	4 / 16	2026-05-29
0.16.5	4 / 16	2026-05-14
0.16.4	4 / 16	2026-05-13
0.16.3	4 / 16	2026-05-13
0.16.2	4 / 16	2026-05-11
0.16.1	4 / 16	2026-04-22
0.16.0	4 / 16	2026-04-09
0.15.30	4 / 16	2026-04-07
0.15.29	4 / 16	2026-04-04
0.15.28	4 / 16	2026-04-03
0.15.27	4 / 16	2026-04-02
0.15.26	4 / 16	2026-04-01
0.15.25	4 / 16	2026-03-31
0.15.24	4 / 16	2026-03-30
0.15.23	4 / 16	2026-03-30
0.15.22	4 / 16	2026-03-28
0.15.21	4 / 16	2026-03-27
0.15.20	4 / 16	2026-03-24
0.15.19	4 / 16	2026-03-17
0.15.18	4 / 16	2026-03-16
0.15.17	4 / 16	2026-03-13
0.15.16	4 / 16	2026-03-12
0.15.15	4 / 16	2026-03-11
0.15.14	4 / 15	2026-03-11
0.15.13	4 / 15	2026-02-25
0.15.12	4 / 15	2026-02-02
0.15.11	4 / 15	2026-01-30
0.15.10	4 / 15	2026-01-28
0.15.9	4 / 15	2026-01-24
0.15.8	4 / 15	2026-01-16
0.15.7	4 / 15	2026-01-09
0.15.6	4 / 15	2026-01-07
0.15.5	4 / 15	2025-12-16
0.15.4	4 / 15	2025-11-19
0.15.3	4 / 15	2025-11-13
0.15.2	4 / 15	2025-11-05
0.15.1	4 / 15	2025-10-31
0.15.0	4 / 15	2025-10-29
0.14.28	4 / 15	2025-10-27
0.14.27	5 / 15	2025-10-27

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.5

1 finding

LOW No provenance attestation provenance

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

v0.16.4

1 finding

LOW No provenance attestation provenance

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

v0.16.3

1 finding

LOW No provenance attestation provenance

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

v0.16.2

1 finding

LOW No provenance attestation provenance

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

v0.16.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.16.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.15.30

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

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-04-04) provenance

This version was published by a different npm account than previous versions on 2026-04-04. 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.15.28

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-04-03) provenance

This version was published by a different npm account than previous versions on 2026-04-03. 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.15.27

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-04-02) provenance

This version was published by a different npm account than previous versions on 2026-04-02. 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.15.26

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-04-01) provenance

This version was published by a different npm account than previous versions on 2026-04-01. 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.15.25

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-31) provenance

This version was published by a different npm account than previous versions on 2026-03-31. 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.15.24

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-30) provenance

This version was published by a different npm account than previous versions on 2026-03-30. 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.15.23

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-30) provenance

This version was published by a different npm account than previous versions on 2026-03-30. 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.15.22

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-28) provenance

This version was published by a different npm account than previous versions on 2026-03-28. 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.15.21

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-27) provenance

This version was published by a different npm account than previous versions on 2026-03-27. 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.15.20

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. 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.15.19

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-17) provenance

This version was published by a different npm account than previous versions on 2026-03-17. 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.15.18

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-16) provenance

This version was published by a different npm account than previous versions on 2026-03-16. 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.15.17

2 findings

HIGH Publisher changed: sarah-inkeep → GitHub Actions (on 2026-03-13) provenance

This version was published by a different npm account than previous versions on 2026-03-13. 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.15.16

1 finding

LOW No provenance attestation provenance

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

v0.15.15

1 finding

LOW No provenance attestation provenance

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

v0.15.14

1 finding

LOW No provenance attestation provenance

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

v0.15.13

1 finding

LOW No provenance attestation provenance

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

v0.15.12

1 finding

LOW No provenance attestation provenance

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

v0.15.11

1 finding

LOW No provenance attestation provenance

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

v0.15.10

1 finding

LOW No provenance attestation provenance

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

v0.15.9

1 finding

LOW No provenance attestation provenance

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

v0.15.8

1 finding

LOW No provenance attestation provenance

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

v0.15.7

1 finding

LOW No provenance attestation provenance

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

v0.15.6

1 finding

LOW No provenance attestation provenance

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

v0.15.5

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

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

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

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

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: abraham-inkeep → sarah-inkeep (on 2025-10-31) provenance

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

v0.15.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: abraham-inkeep → sarah-inkeep (on 2025-10-29) provenance

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

v0.14.28

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

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.