@xylabs/tsconfig
Typescript Base Config used throughout XY Labs TypeScript/JavaScript libraries and react projects
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Config-stub packages legitimately have empty main and minimal docs. | ai | |
| dependencies | unvetted-dep:@ariestools/tsconfig | AI (dependencies): Declared rename target per package.json deprecation notice, not a rogue dep. | ai | |
| provenance | missing-githead | AI (provenance): Low-risk tsconfig-only package; publisher has strong track record; no code execution surface. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email on prior approved versions; not a hostile addition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removal paired with atrouw addition reflects a legitimate maintainer rotation, not a takeover. | ai |
Versions (showing 100 of 268)
| Version | Deps | Published |
|---|---|---|
| 8.7.0 | 1 / 3 | |
| 8.6.12 | 1 / 3 | |
| 8.6.11 | 1 / 3 | |
| 8.6.10 | 0 / 8 | |
| 8.6.9 | 0 / 8 | |
| 8.6.8 | 0 / 8 | |
| 8.6.7 | 0 / 8 | |
| 8.6.6 | 0 / 8 | |
| 8.6.5 | 0 / 8 | |
| 8.6.4 | 0 / 8 | |
| 8.6.3 | 0 / 8 | |
| 8.6.2 | 0 / 9 | |
| 8.6.1 | 0 / 9 | |
| 8.6.0 | 0 / 9 | |
| 8.5.15 | 0 / 9 | |
| 8.5.14 | 0 / 9 | |
| 8.5.13 | 0 / 9 | |
| 8.5.12 | 0 / 9 | |
| 8.5.11 | 0 / 9 | |
| 8.5.10 | 0 / 9 | |
| 8.5.9 | 0 / 9 | |
| 8.5.8 | 0 / 9 | |
| 8.5.7 | 0 / 9 | |
| 8.5.6 | 0 / 9 | |
| 8.5.5 | 0 / 9 | |
| 8.5.4 | 0 / 9 | |
| 8.5.3 | 0 / 9 | |
| 8.5.1 | 0 / 9 | |
| 8.5.0 | 0 / 9 | |
| 8.4.1 | 0 / 9 | |
| 8.4.0 | 0 / 9 | |
| 8.3.0 | 0 / 9 | |
| 8.2.19 | 0 / 9 | |
| 8.2.18 | 0 / 6 | |
| 8.2.17 | 0 / 6 | |
| 8.2.16 | 0 / 6 | |
| 8.2.14 | 0 / 6 | |
| 8.2.13 | 0 / 6 | |
| 8.2.12 | 0 / 6 | |
| 8.2.11 | 0 / 6 | |
| 8.2.10 | 0 / 6 | |
| 8.2.9 | 0 / 6 | |
| 8.2.8 | 0 / 6 | |
| 8.2.7 | 0 / 6 | |
| 8.2.6 | 0 / 6 | |
| 8.2.5 | 0 / 6 | |
| 8.2.4 | 0 / 6 | |
| 8.2.3 | 0 / 6 | |
| 8.2.2 | 0 / 6 | |
| 8.2.1 | 0 / 6 | |
| 8.2.0 | 0 / 6 | |
| 8.1.21 | 0 / 6 | |
| 8.1.20 | 0 / 6 | |
| 8.1.19 | 0 / 6 | |
| 8.1.18 | 0 / 6 | |
| 8.1.17 | 0 / 6 | |
| 8.1.16 | 0 / 6 | |
| 8.1.15 | 0 / 6 | |
| 8.1.14 | 0 / 6 | |
| 8.1.13 | 0 / 6 | |
| 8.1.12 | 0 / 6 | |
| 8.1.11 | 0 / 6 | |
| 8.1.10 | 0 / 6 | |
| 8.1.9 | 0 / 6 | |
| 8.1.8 | 0 / 6 | |
| 8.1.7 | 0 / 6 | |
| 8.1.6 | 0 / 6 | |
| 8.1.5 | 0 / 6 | |
| 8.1.4 | 0 / 6 | |
| 8.1.3 | 0 / 6 | |
| 8.1.2 | 0 / 6 | |
| 8.1.0 | 0 / 6 | |
| 8.0.16 | 0 / 6 | |
| 8.0.15 | 0 / 6 | |
| 8.0.14 | 0 / 6 | |
| 8.0.12 | 0 / 0 | |
| 8.0.10 | 0 / 0 | |
| 8.0.9 | 0 / 0 | |
| 8.0.8 | 0 / 0 | |
| 8.0.7 | 0 / 0 | |
| 8.0.6 | 0 / 0 | |
| 8.0.4 | 0 / 0 | |
| 8.0.3 | 0 / 0 | |
| 8.0.2 | 0 / 0 | |
| 8.0.1 | 0 / 0 | |
| 8.0.0 | 0 / 0 | |
| 7.13.24 | 0 / 0 | |
| 7.13.23 | 0 / 0 | |
| 7.13.22 | 0 / 0 | |
| 7.13.21 | 0 / 0 | |
| 7.13.20 | 0 / 0 | |
| 7.13.19 | 0 / 0 | |
| 7.13.18 | 0 / 0 | |
| 7.13.17 | 0 / 0 | |
| 7.13.16 | 0 / 0 | |
| 7.13.15 | 0 / 0 | |
| 7.13.14 | 0 / 0 | |
| 7.13.13 | 0 / 0 | |
| 7.13.12 | 0 / 0 | |
| 7.13.11 | 0 / 0 |
v8.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
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.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.11
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.6
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.13.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.