@xylabs/tsconfig-react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ariestools/tsconfig-react | AI (phantom-deps): tsconfig deps are referenced via config extends, not imports. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Config-stub package legitimately has no code/README/repo content. | ai | |
| phantom-deps | phantom-dep:@ariestools/tsconfig | AI (phantom-deps): tsconfig deps are referenced via config extends, not imports. | ai | |
| phantom-deps | phantom-dep:@ariestools/tsconfig-dom | AI (phantom-deps): tsconfig deps are referenced via config extends, not imports. | ai | |
| provenance | missing-githead | AI (provenance): Large monorepo with frequent releases; gitHead absence reflects CI toolchain change, not a supply-chain risk for a tsconfig-only package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo batch releases routinely publish many packages in quick succession; stable pattern for xylabs packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email on prior approved versions; not a new external actor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removal paired with atrouw addition is a known-maintainer rotation, not a takeover. | ai |
Versions (showing 100 of 262)
| Version | Deps | Published |
|---|---|---|
| 7.13.10 | 0 / 10 | |
| 7.13.9 | 0 / 10 | |
| 7.13.8 | 0 / 10 | |
| 7.13.7 | 0 / 10 | |
| 7.13.6 | 0 / 10 | |
| 7.13.5 | 0 / 10 | |
| 7.13.4 | 0 / 10 | |
| 7.13.3 | 0 / 10 | |
| 7.13.2 | 0 / 10 | |
| 7.13.1 | 0 / 10 | |
| 7.13.0 | 0 / 10 | |
| 7.12.3 | 0 / 11 | |
| 7.12.2 | 0 / 11 | |
| 7.12.1 | 0 / 11 | |
| 7.12.0 | 0 / 11 | |
| 7.11.12 | 0 / 11 | |
| 7.11.11 | 0 / 11 | |
| 7.11.10 | 0 / 11 | |
| 7.11.9 | 0 / 11 | |
| 7.11.8 | 0 / 11 | |
| 7.11.7 | 0 / 11 | |
| 7.11.6 | 0 / 11 | |
| 7.11.5 | 0 / 11 | |
| 7.11.4 | 0 / 11 | |
| 7.11.3 | 0 / 11 | |
| 7.11.2 | 0 / 30 | |
| 7.11.0 | 0 / 10 | |
| 7.10.9 | 0 / 10 | |
| 7.10.8 | 0 / 9 | |
| 7.10.7 | 0 / 9 | |
| 7.10.5 | 0 / 9 | |
| 7.10.4 | 0 / 9 | |
| 7.10.3 | 0 / 9 | |
| 7.10.2 | 0 / 9 | |
| 7.10.1 | 0 / 9 | |
| 7.10.0 | 0 / 9 | |
| 7.9.10 | 0 / 4 | |
| 7.9.9 | 0 / 4 | |
| 7.9.8 | 0 / 4 | |
| 7.9.7 | 0 / 4 | |
| 7.9.6 | 0 / 4 | |
| 7.9.5 | 0 / 4 | |
| 7.9.4 | 0 / 4 | |
| 7.9.3 | 0 / 4 | |
| 7.9.2 | 0 / 4 | |
| 7.9.1 | 0 / 4 | |
| 7.9.0 | 0 / 4 | |
| 7.8.7 | 0 / 4 | |
| 7.8.6 | 0 / 4 | |
| 7.8.5 | 0 / 4 | |
| 7.8.4 | 1 / 2 | |
| 7.8.3 | 1 / 2 | |
| 7.8.0 | 0 / 4 | |
| 7.7.15 | 1 / 3 | |
| 7.7.14 | 1 / 3 | |
| 7.7.13 | 1 / 3 | |
| 7.7.11 | 0 / 4 | |
| 7.7.10 | 0 / 4 | |
| 7.7.9 | 0 / 4 | |
| 7.7.8 | 0 / 4 | |
| 7.7.7 | 0 / 4 | |
| 7.7.6 | 0 / 4 | |
| 7.7.5 | 0 / 4 | |
| 7.7.4 | 0 / 4 | |
| 7.7.3 | 0 / 4 | |
| 7.7.2 | 0 / 4 | |
| 7.6.21 | 0 / 4 | |
| 7.6.20 | 0 / 4 | |
| 7.6.19 | 0 / 4 | |
| 7.6.18 | 0 / 4 | |
| 7.6.17 | 0 / 4 | |
| 7.6.16 | 0 / 4 | |
| 7.6.15 | 0 / 4 | |
| 7.6.14 | 0 / 4 | |
| 7.6.13 | 0 / 4 | |
| 7.6.12 | 0 / 4 | |
| 7.6.11 | 0 / 4 | |
| 7.6.10 | 0 / 4 | |
| 7.6.9 | 0 / 4 | |
| 7.6.8 | 0 / 4 | |
| 7.6.6 | 0 / 4 | |
| 7.6.5 | 0 / 4 | |
| 7.6.4 | 0 / 4 | |
| 7.6.3 | 0 / 4 | |
| 7.6.2 | 0 / 4 | |
| 7.6.1 | 0 / 4 | |
| 7.6.0 | 0 / 4 | |
| 7.5.17 | 0 / 4 | |
| 7.5.15 | 0 / 4 | |
| 7.5.14 | 0 / 4 | |
| 7.5.13 | 0 / 4 | |
| 7.5.12 | 0 / 4 | |
| 7.5.11 | 0 / 3 | |
| 7.5.10 | 0 / 3 | |
| 7.5.9 | 0 / 3 | |
| 7.5.7 | 0 / 3 | |
| 7.5.6 | 0 / 3 | |
| 7.5.5 | 0 / 3 | |
| 7.5.4 | 0 / 3 | |
| 7.5.3 | 0 / 3 |
v7.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.