← Home

@salesforce/templates

npm Homepage
51
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): salesforce-admin is a Salesforce corporate consolidation account; adding it while removing individual developer accounts is consistent with enterprise access management practices for this publisher. ai
maintainer-change maintainer-removed AI (maintainer-change): Mass removal of individual developer maintainers in favor of a corporate admin account is consistent with Salesforce's enterprise access consolidation pattern for this publisher. ai
bogus-package bogus-package AI (bogus-package): Established Salesforce enterprise package; minimal npm README and no keywords are typical for this org's packages and not indicative of spam or phishing. ai

Versions (showing 51 of 52)

View all versions
Version Deps Published
66.9.1 8 / 38
66.9.0 8 / 38
66.8.0 8 / 38
66.7.13 8 / 38
66.7.12 8 / 38
66.7.11 8 / 38
66.7.10 8 / 38
66.7.9 8 / 38
66.7.8 8 / 38
66.7.7 8 / 38
66.7.6 8 / 38
66.7.5 8 / 38
66.7.4 8 / 38
66.7.3 8 / 38
66.7.2 8 / 38
66.7.1 8 / 38
66.7.0 8 / 38
66.6.2 8 / 38
66.6.1 8 / 38
66.6.0 8 / 38
66.5.6 8 / 38
66.5.5 8 / 38
66.5.4 8 / 38
66.5.3 8 / 38
66.5.2 8 / 38
66.5.1 8 / 38
66.5.0 8 / 38
66.4.2 8 / 38
66.4.1 8 / 38
66.4.0 8 / 38
66.3.3 8 / 38
66.3.2 8 / 38
66.3.1 8 / 38
66.3.0 8 / 38
66.2.1 8 / 38
66.2.0 8 / 38
66.1.1 8 / 36
66.1.0 8 / 36
65.5.11 8 / 36
65.5.10 8 / 36
65.5.9 8 / 36
65.5.8 8 / 36
65.4.4 8 / 34
65.4.3 8 / 34
65.4.2 8 / 34
65.4.1 8 / 34
65.4.0 8 / 34
65.3.0 8 / 34
65.2.0 8 / 34
65.1.3 8 / 34
65.1.2 8 / 34

v66.9.1

1 finding
LOW No provenance attestation provenance

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

v66.9.0

1 finding
LOW No provenance attestation provenance

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

v66.8.0

1 finding
LOW No provenance attestation provenance

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

v66.7.13

1 finding
LOW No provenance attestation provenance

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

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

v66.7.11

1 finding
LOW No provenance attestation provenance

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

v66.7.10

1 finding
LOW No provenance attestation provenance

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

v66.7.9

1 finding
LOW No provenance attestation provenance

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

v66.7.8

1 finding
LOW No provenance attestation provenance

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

v66.7.7

1 finding
LOW No provenance attestation provenance

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

v66.7.6

1 finding
LOW No provenance attestation provenance

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

v66.7.5

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

v66.5.1

1 finding
LOW No provenance attestation provenance

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

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