← Home

@salesforce/telemetry

npm Repository Homepage
100
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

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

Keywords

forcesalesforcesfdxsalesforcedxsfdx-command

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Salesforce-releases is a known, trusted publisher with 1103 approved packages. Lack of Sigstore provenance is a minor gap, not a security concern for this established package. ai

Versions (showing 100 of 122)

Version Deps Published
6.8.40 7 / 3
6.8.39 7 / 3
6.8.38 7 / 3
6.8.37 7 / 3
6.8.36 7 / 3
6.8.35 7 / 3
6.8.34 7 / 3
6.8.33 7 / 3
6.8.32 7 / 3
6.8.31 7 / 3
6.8.30 7 / 3
6.8.29 7 / 3
6.8.28 7 / 3
6.8.27 7 / 3
6.8.26 7 / 3
6.8.25 7 / 3
6.8.24 7 / 3
6.8.23 7 / 3
6.8.22 7 / 3
6.8.21 7 / 3
6.8.20 7 / 3
6.8.19 7 / 3
6.8.18 7 / 3
6.8.17 7 / 3
6.8.16 7 / 3
6.8.15 7 / 3
6.8.14 7 / 3
6.8.13 7 / 3
6.8.12 7 / 3
6.8.11 7 / 3
6.8.10 7 / 3
6.8.9 7 / 3
6.8.8 7 / 3
6.8.7 7 / 3
6.8.6 7 / 3
6.8.5 7 / 3
6.8.4 7 / 3
6.8.3 7 / 3
6.8.2 7 / 3
6.8.1 7 / 3
6.8.0 7 / 3
6.7.3 7 / 3
6.7.2 7 / 3
6.7.1 7 / 3
6.7.0 7 / 3
6.6.7 7 / 3
6.6.6 7 / 3
6.6.5 7 / 3
6.6.4 7 / 3
6.6.3 7 / 3
6.6.2 7 / 3
6.6.1 7 / 3
6.6.0 7 / 3
6.5.2 6 / 3
6.5.1 6 / 3
6.5.0 6 / 3
6.4.8 6 / 3
6.4.7 6 / 3
6.4.6 6 / 3
6.4.5 6 / 3
6.4.3 6 / 3
6.4.2 6 / 3
6.4.1 6 / 3
6.4.0 6 / 3
6.3.1 6 / 3
6.3.0 6 / 3
6.2.13 6 / 3
6.2.12 6 / 3
6.2.11 6 / 3
6.2.10 6 / 3
6.2.9 6 / 3
6.2.8 6 / 3
6.2.7 6 / 3
6.2.6 6 / 3
6.2.5 6 / 3
6.2.4 6 / 3
6.2.3 6 / 3
6.2.2 6 / 3
6.2.1 6 / 3
6.2.0 6 / 3
6.1.1 6 / 3
6.1.0 6 / 3
6.0.39 5 / 3
6.0.38 5 / 3
6.0.37 5 / 3
6.0.36 5 / 3
6.0.35 5 / 3
6.0.34 5 / 3
6.0.33 5 / 3
6.0.32 5 / 3
6.0.31 5 / 3
6.0.30 5 / 3
6.0.29 5 / 3
6.0.28 5 / 3
6.0.27 5 / 3
6.0.26 5 / 3
6.0.25 5 / 3
6.0.24 5 / 3
6.0.23 5 / 3
6.0.22 5 / 3
Showing 100 of 122 Next page →

v6.8.40

1 finding
INFO No provenance attestation provenance

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

v6.8.39

1 finding
INFO No provenance attestation provenance

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

v6.8.38

1 finding
INFO No provenance attestation provenance

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

v6.8.37

1 finding
INFO No provenance attestation provenance

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

v6.8.36

1 finding
INFO No provenance attestation provenance

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

v6.8.35

1 finding
INFO No provenance attestation provenance

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

v6.8.34

1 finding
INFO No provenance attestation provenance

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

v6.8.33

1 finding
INFO No provenance attestation provenance

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

v6.0.39

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.38

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.37

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.36

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.0.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.