@adobe/data
Adobe data oriented programming library
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used to generate typed-buffer struct readers from layout metadata; controlled input, not user-supplied arbitrary code. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Binary is a WASM/native artifact from the documented AssemblyScript build pipeline; stable for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy get trap for transparent property forwarding — idiomatic JS, not obfuscation. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/card | AI (dependencies): Adobe's official Spectrum Web Components library; expected dep for this Adobe package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/action-group | AI (dependencies): Adobe's official Spectrum Web Components library; expected dep for this Adobe package. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Lit context referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/card | AI (phantom-deps): SWC components loaded via side-effect/HTML; not directly imported in JS but legitimately used. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/theme | AI (phantom-deps): SWC components loaded via side-effect/HTML; not directly imported in JS but legitimately used. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/styles | AI (phantom-deps): SWC components loaded via side-effect/HTML; not directly imported in JS but legitimately used. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/button | AI (phantom-deps): SWC components loaded via side-effect/HTML; not directly imported in JS but legitimately used. | ai |
Versions (showing 23 of 129)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 4 / 37 | |
| 0.4.1 | 4 / 37 | |
| 0.4.0 | 4 / 37 | |
| 0.3.3 | 4 / 37 | |
| 0.3.2 | 4 / 37 | |
| 0.3.1 | 4 / 37 | |
| 0.3.0 | 4 / 37 | |
| 0.2.13 | 4 / 37 | |
| 0.2.12 | 4 / 37 | |
| 0.2.11 | 4 / 37 | |
| 0.2.10 | 4 / 37 | |
| 0.2.9 | 4 / 37 | |
| 0.2.8 | 4 / 37 | |
| 0.2.7 | 4 / 37 | |
| 0.2.6 | 4 / 37 | |
| 0.2.5 | 4 / 37 | |
| 0.2.4 | 4 / 37 | |
| 0.2.3 | 4 / 37 | |
| 0.2.2 | 4 / 37 | |
| 0.2.1 | 4 / 37 | |
| 0.2.0 | 4 / 37 | |
| 0.1.3 | 2 / 35 | |
| 0.1.2 | 1 / 35 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
2 findingsPackage contains compiled binaries that could be backdoors: • c/vector_addition
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • c/vector_addition
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.