@sassoftware/va-report-components
The SAS Visual Analytics SDK is a set of JavaScript APIs and web components that enable SAS Visual Analytics report content to be easily embedded in a third-party application or web page.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:redux | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:polished | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:reselect | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:cldr-core | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-dnd | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-popper | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:use-memo-one | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-cropper | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Bundled package; deps compiled into dist artifacts, not directly imported in analyzable source. | ai |
v2.34.0
27 findingsDeclared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.