@operato/data-tree
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lit | AI (phantom-deps): Runtime dependency for web component; declared and used as expected. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Runtime dependency for i18n; declared and used as expected. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Runtime dependency; declared and used as expected. | ai | |
| phantom-deps | phantom-dep:@operato/styles | AI (phantom-deps): Same-org scoped dependency; declared and used as expected. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.2.12 | 4 / 18 | |
| 9.1.0 | 4 / 18 | |
| 9.0.34 | 4 / 18 | |
| 9.0.2 | 4 / 18 | |
| 9.0.1 | 4 / 18 | |
| 9.0.0 | 4 / 18 |
v9.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.