@kitschpatrol/repo-config
Repository configuration and GitHub workflows for @kitschpatrol/shared-config.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:decircular | AI (dependencies): Small circular-reference utility; no malicious indicators, used as a config helper dep. | ai | |
| dependencies | unvetted-dep:@pinojs/json-colorizer | AI (dependencies): Official pino-ecosystem JSON colorizer; benign logging utility. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 97 versions and verified GitHub repo; dormancy pattern not indicative of takeover here. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:decircular | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:package-up | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:cosmiconfig | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:find-workspaces | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@pnpm/lockfile.fs | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@pinojs/json-colorizer | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:cosmiconfig-typescript-loader | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:json-stringify-pretty-compact | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:globby | AI (phantom-deps): Config/CLI tool pattern; deps referenced in config files, not direct imports. Stable FP for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.6.3 | 16 / 0 | |
| 7.6.2 | 16 / 0 | |
| 7.6.1 | 16 / 0 | |
| 7.6.0 | 16 / 0 | |
| 7.5.3 | 16 / 0 | |
| 7.5.2 | 16 / 0 | |
| 7.4.0 | 16 / 0 | |
| 7.3.0 | 16 / 0 | |
| 7.1.0 | 16 / 0 | |
| 7.0.0 | 16 / 0 | |
| 6.2.0 | 16 / 0 | |
| 6.0.2 | 16 / 0 | |
| 6.0.1 | 16 / 0 | |
| 5.9.1 | 7 / 1 | |
| 5.9.0 | 7 / 1 | |
| 5.8.1 | 7 / 1 | |
| 5.8.0 | 7 / 1 |
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.