@tachybase/data-source
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): JWT library used in config/type resolution; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/jsonwebtoken | AI (phantom-deps): Type package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tachybase/cache | AI (phantom-deps): Same-org scoped dep; monorepo convention, not a real phantom dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is a consistent pattern across all @tachybase/* packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this monorepo; not indicative of malicious intent. | ai | |
| dependencies | unvetted-dep:@tachybase/acl | AI (dependencies): Sibling monorepo package pinned to same version; coordinated release pattern. | ai | |
| dependencies | unvetted-dep:@tachybase/utils | AI (dependencies): Sibling monorepo package pinned to same version; coordinated release pattern. | ai | |
| dependencies | unvetted-dep:@tachybase/database | AI (dependencies): Sibling monorepo package pinned to same version; coordinated release pattern. | ai | |
| dependencies | unvetted-dep:@tachybase/actions | AI (dependencies): Sibling monorepo package pinned to same version; coordinated release pattern. | ai | |
| dependencies | unvetted-dep:@tachybase/resourcer | AI (dependencies): Sibling monorepo package pinned to same version; coordinated release pattern. | ai |
Versions (showing 51 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.6.12 | 8 / 7 | |
| 1.6.11 | 8 / 7 | |
| 1.6.10 | 8 / 7 | |
| 1.6.9 | 8 / 7 | |
| 1.6.3 | 8 / 7 | |
| 1.6.2 | 8 / 7 | |
| 1.6.1 | 8 / 7 | |
| 1.6.0 | 8 / 7 | |
| 1.3.54 | 8 / 7 | |
| 1.3.53 | 8 / 7 | |
| 1.3.52 | 8 / 7 | |
| 1.3.51 | 8 / 7 | |
| 1.3.50 | 8 / 7 | |
| 1.3.49 | 8 / 7 | |
| 1.3.48 | 8 / 7 | |
| 1.3.47 | 8 / 7 | |
| 1.3.46 | 8 / 7 | |
| 1.3.45 | 8 / 7 | |
| 1.3.44 | 8 / 7 | |
| 1.3.43 | 8 / 7 | |
| 1.3.42 | 8 / 7 | |
| 1.3.41 | 8 / 7 | |
| 1.3.40 | 8 / 7 | |
| 1.3.39 | 8 / 7 | |
| 1.3.38 | 8 / 7 | |
| 1.3.37 | 8 / 7 | |
| 1.3.36 | 8 / 7 | |
| 1.3.35 | 8 / 7 | |
| 1.3.34 | 11 / 7 | |
| 1.3.33 | 11 / 7 | |
| 1.3.32 | 8 / 7 | |
| 1.3.31 | 8 / 7 | |
| 1.3.30 | 8 / 7 | |
| 1.3.29 | 11 / 7 | |
| 1.3.28 | 11 / 7 | |
| 1.3.27 | 11 / 7 | |
| 1.3.26 | 11 / 7 | |
| 1.3.25 | 11 / 7 | |
| 1.3.24 | 11 / 7 | |
| 1.3.23 | 11 / 7 | |
| 1.3.22 | 11 / 7 | |
| 1.3.21 | 11 / 7 | |
| 1.3.20 | 11 / 7 | |
| 1.3.19 | 11 / 7 | |
| 1.3.18 | 11 / 7 | |
| 1.3.17 | 11 / 7 | |
| 1.3.16 | 11 / 7 | |
| 1.3.15 | 11 / 7 | |
| 1.3.14 | 11 / 7 | |
| 1.3.13 | 11 / 7 | |
| 1.3.12 | 11 / 7 |
v1.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.