@salesforce/mcp-provider-aura-experts
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal Salesforce tool; minimal metadata is expected for internal-use packages. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@salesforce/telemetry | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai | |
| phantom-deps | phantom-dep:eventsource | AI (phantom-deps): Bundled tool; dependencies referenced in config, not direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 11 / 14 | |
| 0.3.6 | 11 / 14 | |
| 0.3.5 | 11 / 14 | |
| 0.3.4 | 11 / 14 | |
| 0.3.3 | 12 / 14 | |
| 0.3.2 | 12 / 14 | |
| 0.3.0 | 12 / 14 |
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.