← Home

@salesforce/code-analyzer-sfge-engine

npm Repository Homepage
3
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 org consolidating to salesforce-admin account; consistent with enterprise maintainer management. ai
maintainer-change maintainer-removed AI (maintainer-change): Mass removal of individual contributors in favor of org account; expected pattern for Salesforce packages. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only dependency used at compile time, not imported directly at runtime. ai

Versions (showing 3 of 3)

Version Deps Published
0.21.0 3 / 9
0.20.0 3 / 9
0.13.0 3 / 9

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

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