@servicetitan/anvil2-ext-atlas ISC 30 versions

@servicetitan/anvil2-ext-atlas

npm

This package contains the UI components used in the Atlas chat experience. These components are built using Anvil2, and are maintained by both the Atlas and Anvil teams.

30

Versions

ISC

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

st-teamrgdelatojesspkarpoffseanmadidextersealy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:tabbable	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:classnames	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:tinycolor2	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:react-markdown	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:@react-hook/merged-ref	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21
phantom-deps	phantom-dep:@react-hook/resize-observer	AI (phantom-deps): Declared dependency; used indirectly in codebase.	ai	2026/05/21

Versions (showing 30 of 30)

Version	Deps	Published
2.1.2	9 / 44	2026-05-18
2.1.1	9 / 44	2026-05-13
2.1.0	9 / 44	2026-05-08
2.0.3	9 / 44	2026-04-30
2.0.2	9 / 44	2026-04-28
2.0.1	9 / 44	2026-04-24
2.0.0	9 / 44	2026-04-21
1.4.0	9 / 44	2026-05-08
1.3.0	9 / 44	2026-04-14
1.2.3	9 / 44	2026-03-12
1.2.2	9 / 44	2026-03-10
1.2.1	9 / 44	2026-02-11
1.2.0	9 / 44	2026-02-03
1.1.0	9 / 44	2026-01-23
1.0.0	9 / 44	2026-01-21
0.1.1	9 / 44	2026-01-08
0.1.0	9 / 44	2025-12-22
0.0.14	7 / 40	2025-12-19
0.0.13	7 / 40	2025-12-16
0.0.12	7 / 40	2025-12-10
0.0.11	7 / 40	2025-12-09
0.0.10	7 / 40	2025-12-03
0.0.9	7 / 40	2025-11-26
0.0.8	7 / 40	2025-11-25
0.0.7	7 / 40	2025-11-24
0.0.6	7 / 40	2025-11-21
0.0.5	7 / 40	2025-11-14
0.0.4	7 / 40	2025-11-12
0.0.3	7 / 40	2025-11-04
0.0.2	7 / 40	2025-11-04

v2.1.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.

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

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

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

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

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

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

v1.4.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.3.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.2.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.

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

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

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

v0.0.14

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

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

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

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

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

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

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