@salesforce/plugin-orchestrator

Plugin for working with SalesForce analytic apps, templates, assets and services.

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

demianbrechtjye-sfjburniekevinv11nbyaopmdartusjcourtnerdferroduane.chewravi.jayaramappamjrustapapkojleen-sfdcjqiancwallsfdhagberg-sfkhawkinsmbettioamphroire-npm-team-userdamilareolowoniyijodarovesfdctakafernomacjimjagivarleyjbartolotta-sfdcdhersammmadialagandbreese-salesforceashokrudrarajusalesforce-releasesiamazizpackagellamahkiiadirasanamnolanlawsonjasonschroeder-sfdcdanielshoxdme722mawardjmsjtumobifydlouvtonlwc-adminabirchfieldsfdcww951206

Keywords

forcesalesforcesalesforcedxsfsf-pluginsfdxsfdx-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:eslint-config-salesforce-license	AI (phantom-deps): Lint config dep from same Salesforce org; declared but used only in eslint config, not directly imported in source.	ai	2026/05/09
provenance	no-provenance	AI (provenance): Salesforce-releases is a well-established publisher; lack of Sigstore provenance is common and not a risk signal here.	ai	2026/05/09
phantom-deps	phantom-dep:eslint	AI (phantom-deps): eslint is declared and used in build scripts/config; stable false positive.	ai	2026/04/28
phantom-deps	phantom-dep:@salesforce/kit	AI (phantom-deps): Same-org scope dependency; declared and used; stable false positive.	ai	2026/04/28
phantom-deps	phantom-dep:@inquirer/select	AI (phantom-deps): Declared dependency used in config; stable false positive.	ai	2026/04/28

Versions (showing 47 of 47)

Version	Deps	Published
1.1.0	7 / 9	2025-12-05
1.0.52	7 / 10	2026-05-31
1.0.51	7 / 10	2026-05-24
1.0.50	7 / 10	2026-05-17
1.0.49	7 / 10	2026-05-10
1.0.48	7 / 10	2026-05-09
1.0.47	7 / 10	2026-05-09
1.0.46	7 / 10	2026-05-03
1.0.45	7 / 10	2026-04-26
1.0.44	7 / 10	2026-04-26
1.0.43	7 / 10	2026-04-26
1.0.41	7 / 10	2026-04-05
1.0.40	7 / 10	2026-03-29
1.0.39	7 / 10	2026-03-27
1.0.38	7 / 10	2026-03-23
1.0.37	7 / 10	2026-03-22
1.0.36	7 / 10	2026-03-22
1.0.35	7 / 9	2026-03-15
1.0.34	7 / 9	2026-03-08
1.0.33	7 / 9	2026-03-08
1.0.32	7 / 9	2026-03-01
1.0.31	7 / 9	2026-02-08
1.0.30	7 / 9	2026-01-25
1.0.29	7 / 9	2026-01-24
1.0.28	7 / 9	2026-01-18
1.0.27	7 / 9	2026-01-18
1.0.26	7 / 9	2026-01-09
1.0.25	7 / 9	2025-12-21
1.0.24	7 / 9	2025-12-11
1.0.23	7 / 9	2025-12-09
1.0.22	7 / 9	2025-12-08
1.0.21	7 / 9	2025-12-07
1.0.20	7 / 9	2025-12-05
1.0.18	6 / 9	2025-10-01
1.0.17	6 / 9	2025-09-07
1.0.16	6 / 9	2025-08-31
1.0.15	6 / 9	2025-08-24
1.0.14	6 / 9	2025-08-10
1.0.13	6 / 9	2025-07-28
1.0.12	6 / 9	2025-07-27
1.0.11	6 / 9	2025-07-22
1.0.10	6 / 9	2025-07-22
1.0.9	6 / 9	2025-07-13
1.0.8	6 / 9	2025-07-13
1.0.7	6 / 9	2025-07-06
1.0.6	6 / 8	2025-07-02
1.0.0	6 / 8	2025-07-02

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

1 finding

INFO No provenance attestation provenance

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

v1.0.51

1 finding

INFO No provenance attestation provenance

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

v1.0.50

1 finding

INFO No provenance attestation provenance

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

v1.0.49

1 finding

INFO No provenance attestation provenance

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

v1.0.48

1 finding

INFO No provenance attestation provenance

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

v1.0.47

1 finding

INFO No provenance attestation provenance

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

v1.0.46

1 finding

INFO No provenance attestation provenance

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

v1.0.45

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

1 finding

LOW No provenance attestation provenance

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

v1.0.43

1 finding

LOW No provenance attestation provenance

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

v1.0.41

1 finding

LOW No provenance attestation provenance

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

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

1 finding

LOW No provenance attestation provenance

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

v1.0.25

1 finding

LOW No provenance attestation provenance

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

v1.0.24

1 finding

LOW No provenance attestation provenance

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

v1.0.23

1 finding

LOW No provenance attestation provenance

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

v1.0.22

1 finding

LOW No provenance attestation provenance

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

v1.0.21

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

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

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

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.