@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 51 of 123)
| Version | Deps | Published |
|---|---|---|
| 0.9.63 | 3 / 35 | |
| 0.9.62 | 3 / 35 | |
| 0.9.61 | 3 / 35 | |
| 0.9.60 | 3 / 35 | |
| 0.9.59 | 3 / 35 | |
| 0.9.58 | 3 / 35 | |
| 0.9.57 | 3 / 35 | |
| 0.9.56 | 3 / 35 | |
| 0.9.55 | 3 / 35 | |
| 0.9.54 | 3 / 35 | |
| 0.9.53 | 3 / 35 | |
| 0.9.52 | 3 / 35 | |
| 0.9.51 | 3 / 35 | |
| 0.9.50 | 3 / 35 | |
| 0.9.48 | 3 / 35 | |
| 0.9.47 | 3 / 35 | |
| 0.9.46 | 3 / 35 | |
| 0.9.45 | 3 / 35 | |
| 0.9.44 | 3 / 35 | |
| 0.9.43 | 3 / 35 | |
| 0.9.42 | 3 / 35 | |
| 0.9.41 | 3 / 35 | |
| 0.9.40 | 3 / 35 | |
| 0.9.39 | 3 / 35 | |
| 0.9.37 | 3 / 35 | |
| 0.9.36 | 3 / 35 | |
| 0.9.35 | 3 / 35 | |
| 0.9.34 | 3 / 35 | |
| 0.9.33 | 2 / 35 | |
| 0.9.32 | 2 / 35 | |
| 0.9.31 | 2 / 35 | |
| 0.9.30 | 2 / 35 | |
| 0.9.29 | 2 / 35 | |
| 0.9.28 | 2 / 35 | |
| 0.9.27 | 2 / 35 | |
| 0.9.26 | 2 / 35 | |
| 0.9.25 | 2 / 35 | |
| 0.9.24 | 2 / 35 | |
| 0.9.23 | 2 / 35 | |
| 0.9.22 | 2 / 35 | |
| 0.9.21 | 2 / 35 | |
| 0.9.20 | 2 / 35 | |
| 0.9.19 | 2 / 35 | |
| 0.9.17 | 2 / 35 | |
| 0.9.16 | 2 / 35 | |
| 0.9.11 | 2 / 35 | |
| 0.9.7 | 11 / 38 | |
| 0.9.6 | 11 / 38 | |
| 0.9.5 | 11 / 38 | |
| 0.9.4 | 11 / 38 | |
| 0.9.2 | 11 / 38 |
v0.9.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.