@salesforce/apex-node No license 56 versions

@salesforce/apex-node

npm Homepage

56

Versions

—

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

ire-npm-team-userjimjagsalesforce-releasesjasonschroeder-sfdcmobifylwc-adminsalesforce-admin

Keywords

apexforcesalesforcesfdxsalesforcedx

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get() used in type-narrowing utility code; benign pattern stable across versions of this package.	ai	2026/05/09
bogus-package	bogus-package	AI (bogus-package): Established @salesforce scoped package with 187 versions and official GitHub repo. README linking to external Salesforce docs is expected; not a phishing link farm.	ai	2026/04/26
phantom-deps	phantom-dep:@types/istanbul-reports	AI (phantom-deps): @types/istanbul-reports is a TypeScript type package; its presence in runtime deps is a packaging quirk, not a security concern for this established library.	ai	2026/04/26

Versions (showing 56 of 56)

Version	Deps	Published
8.4.27	9 / 32	2026-05-31
8.4.26	9 / 32	2026-05-17
8.4.25	9 / 32	2026-05-10
8.4.24	9 / 32	2026-05-09
8.4.23	9 / 32	2026-05-09
8.4.22	9 / 32	2026-04-19
8.4.21	9 / 32	2026-04-08
8.4.20	9 / 32	2026-04-05
8.4.19	9 / 32	2026-04-05
8.4.18	9 / 32	2026-03-30
8.4.17	9 / 32	2026-03-29
8.4.16	9 / 32	2026-03-26
8.4.15	9 / 32	2026-03-22
8.4.14	9 / 32	2026-03-21
8.4.13	9 / 32	2026-03-19
8.4.12	9 / 32	2026-03-15
8.4.11	9 / 32	2026-03-01
8.4.10	9 / 32	2026-02-23
8.4.9	9 / 32	2026-02-22
8.4.8	9 / 32	2026-02-15
8.4.7	9 / 32	2026-02-10
8.4.6	9 / 32	2026-02-08
8.4.5	9 / 32	2026-01-22
8.4.4	9 / 32	2026-01-18
8.4.3	9 / 32	2026-01-07
8.4.2	9 / 32	2025-12-07
8.4.1	9 / 32	2025-12-05
8.4.0	9 / 32	2025-12-03
8.3.8	9 / 32	2025-11-20
8.3.7	9 / 32	2025-11-13
8.3.6	9 / 32	2025-11-02
8.2.13	9 / 30	2025-09-07
8.2.12	9 / 30	2025-09-07
8.2.11	9 / 30	2025-08-31
8.2.10	9 / 30	2025-08-24
8.2.9	9 / 30	2025-08-24
8.2.8	9 / 31	2025-08-10
8.2.7	9 / 31	2025-08-03
8.2.6	9 / 31	2025-07-27
8.2.5	9 / 31	2025-07-24
8.2.4	9 / 31	2025-07-22
8.2.3	9 / 31	2025-07-13
8.2.2	9 / 31	2025-07-06
8.2.1	9 / 31	2025-06-29
8.2.0	9 / 31	2025-06-26
8.1.33	9 / 31	2025-06-22
8.1.32	9 / 31	2025-06-15
8.1.31	9 / 31	2025-06-08
8.1.30	9 / 31	2025-06-01
8.1.29	10 / 33	2025-05-25
8.1.28	10 / 33	2025-05-25
8.1.27	10 / 33	2025-05-18
8.1.26	10 / 33	2025-05-11
8.1.25	10 / 33	2025-05-04
8.1.24	10 / 33	2025-04-27
8.1.23	10 / 33	2025-04-27

v8.4.27

1 finding

LOW No provenance attestation provenance

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

v8.4.26

1 finding

LOW No provenance attestation provenance

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

v8.4.25

1 finding

LOW No provenance attestation provenance

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

v8.4.24

1 finding

LOW No provenance attestation provenance

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

v8.4.23

1 finding

LOW No provenance attestation provenance

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

v8.4.22

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.

v8.4.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.

v8.4.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.

v8.4.19

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.

v8.4.18

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.

v8.4.17

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.

v8.4.16

1 finding

LOW No provenance attestation provenance

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

v8.4.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.

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

v8.2.13

1 finding

LOW No provenance attestation provenance

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

v8.2.12

1 finding

LOW No provenance attestation provenance

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

v8.2.11

1 finding

LOW No provenance attestation provenance

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

v8.2.10

1 finding

LOW No provenance attestation provenance

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

v8.2.9

1 finding

LOW No provenance attestation provenance

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

v8.2.8

1 finding

LOW No provenance attestation provenance

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

v8.2.7

1 finding

LOW No provenance attestation provenance

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

v8.2.6

1 finding

LOW No provenance attestation provenance

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

v8.2.5

1 finding

LOW No provenance attestation provenance

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

v8.2.4

1 finding

LOW No provenance attestation provenance

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

v8.2.3

1 finding

LOW No provenance attestation provenance

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

v8.2.2

1 finding

LOW No provenance attestation provenance

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

v8.2.1

1 finding

LOW No provenance attestation provenance

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

v8.2.0

1 finding

LOW No provenance attestation provenance

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

v8.1.33

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.

v8.1.32

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.

v8.1.31

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.

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

v8.1.29

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.

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

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

v8.1.26

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.

v8.1.25

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.

v8.1.24

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.

v8.1.23

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.