@truedat/se
Truedat Web Search Engine
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 org package with 942 versions; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @truedat org package with 942 versions; not a typosquat of qs. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:redux | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:is-url | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:is-hotkey | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:react-csv | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:query-string | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:react-moment | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:@apollo/client | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:react-dropzone | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Monorepo pattern; deps declared at package level, consumed via shared config. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 8.6.7 | 26 / 8 | |
| 8.6.6 | 26 / 8 | |
| 8.6.5 | 26 / 8 | |
| 8.6.3 | 26 / 8 | |
| 8.6.2 | 26 / 8 | |
| 8.6.1 | 26 / 8 | |
| 8.6.0 | 26 / 8 | |
| 8.5.10 | 26 / 8 | |
| 8.5.9 | 26 / 8 | |
| 8.5.8 | 26 / 8 | |
| 8.5.7 | 26 / 8 | |
| 8.5.6 | 26 / 8 | |
| 8.5.4 | 26 / 8 | |
| 8.5.3 | 26 / 8 | |
| 8.5.2 | 26 / 8 | |
| 8.5.1 | 26 / 8 | |
| 8.4.10 | 26 / 8 | |
| 8.4.9 | 26 / 8 | |
| 8.4.8 | 26 / 8 | |
| 8.4.7 | 26 / 8 | |
| 8.4.6 | 26 / 8 | |
| 8.4.5 | 26 / 8 | |
| 8.4.4 | 26 / 8 | |
| 8.4.3 | 26 / 8 | |
| 8.4.2 | 26 / 8 | |
| 8.4.1 | 26 / 8 | |
| 8.3.7 | 26 / 8 | |
| 8.3.6 | 26 / 8 | |
| 8.3.5 | 26 / 8 | |
| 8.3.4 | 26 / 8 | |
| 8.3.3 | 26 / 8 | |
| 8.3.2 | 26 / 8 | |
| 8.3.1 | 26 / 8 | |
| 8.3.0 | 26 / 8 | |
| 8.2.4 | 26 / 8 | |
| 8.2.3 | 26 / 8 | |
| 8.2.2 | 26 / 8 | |
| 8.2.1 | 26 / 8 | |
| 8.2.0 | 26 / 8 | |
| 8.1.5 | 26 / 8 | |
| 8.1.4 | 26 / 8 | |
| 8.1.3 | 26 / 8 | |
| 8.1.1 | 26 / 8 | |
| 8.1.0 | 26 / 8 | |
| 8.0.4 | 26 / 8 | |
| 8.0.3 | 26 / 8 | |
| 8.0.2 | 26 / 8 | |
| 8.0.1 | 26 / 8 | |
| 8.0.0 | 26 / 8 | |
| 7.14.5 | 26 / 8 | |
| 7.14.3 | 26 / 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v8.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.