@truedat/dd
Truedat Web Data Dictionary
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @truedat package; Levenshtein match to 'pg' is a false positive for this established org package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @truedat package; Levenshtein match to 'qs' is a false positive for this established org package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @truedat package; Levenshtein match to 'zod' is a false positive for this established org package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:is-url | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:is-hotkey | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:react-csv | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React component library; react-dom is a standard peer dep pattern, not a true phantom. | ai | |
| phantom-deps | phantom-dep:react-dropzone | AI (phantom-deps): React component library; deps may be used indirectly or in config/test contexts not detected by static import analysis. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 8.6.7 | 28 / 8 | |
| 8.6.6 | 28 / 8 | |
| 8.6.5 | 28 / 8 | |
| 8.6.3 | 28 / 8 | |
| 8.6.2 | 28 / 8 | |
| 8.6.1 | 28 / 8 | |
| 8.6.0 | 28 / 8 | |
| 8.5.10 | 28 / 8 | |
| 8.5.9 | 28 / 8 | |
| 8.5.8 | 28 / 8 | |
| 8.5.7 | 28 / 8 | |
| 8.5.6 | 28 / 8 | |
| 8.5.4 | 28 / 8 | |
| 8.5.3 | 28 / 8 | |
| 8.5.2 | 28 / 8 | |
| 8.5.1 | 28 / 8 | |
| 8.4.10 | 28 / 8 | |
| 8.4.9 | 28 / 8 | |
| 8.4.8 | 28 / 8 | |
| 8.4.7 | 28 / 8 | |
| 8.4.6 | 28 / 8 | |
| 8.4.5 | 28 / 8 | |
| 8.4.4 | 28 / 8 | |
| 8.4.3 | 28 / 8 | |
| 8.4.2 | 28 / 8 | |
| 8.4.1 | 28 / 8 | |
| 8.3.7 | 28 / 8 | |
| 7.14.3 | 28 / 8 | |
| 7.14.2 | 28 / 8 | |
| 7.14.1 | 28 / 8 | |
| 7.14.0 | 28 / 8 | |
| 7.13.10 | 28 / 8 | |
| 7.13.9 | 28 / 8 | |
| 7.13.8 | 28 / 8 | |
| 7.13.7 | 28 / 8 | |
| 7.13.6 | 28 / 8 | |
| 7.13.5 | 28 / 8 | |
| 7.13.4 | 28 / 8 | |
| 7.13.3 | 28 / 8 | |
| 7.13.2 | 28 / 8 | |
| 7.13.1 | 28 / 8 | |
| 7.12.10 | 28 / 8 | |
| 7.12.9 | 28 / 8 |
v8.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.