@kitschpatrol/mdat-config
MDAT configuration 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:mdat | AI (dependencies): mdat is the core tool this config package wraps; its presence as a dependency is expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk indicator here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has prior approved package; no material changes from last version; config wrapper in a known monorepo. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:decircular | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:package-up | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:find-workspaces | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:@pinojs/json-colorizer | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:cosmiconfig-typescript-loader | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:json-stringify-pretty-compact | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:cosmiconfig | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Config package re-exports deps for consumers; phantom-dep false positive pattern stable across versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 7.6.3 | 14 / 0 | |
| 7.6.2 | 14 / 0 | |
| 7.6.1 | 14 / 0 | |
| 7.6.0 | 14 / 0 | |
| 7.5.3 | 14 / 0 | |
| 7.5.2 | 14 / 0 | |
| 7.5.1 | 14 / 0 | |
| 7.5.0 | 14 / 0 | |
| 7.4.1 | 14 / 0 | |
| 7.4.0 | 14 / 0 | |
| 7.3.0 | 14 / 0 | |
| 7.2.0 | 14 / 0 | |
| 7.1.0 | 14 / 0 | |
| 7.0.2 | 14 / 0 | |
| 7.0.1 | 14 / 0 | |
| 7.0.0 | 14 / 0 | |
| 6.2.0 | 14 / 0 | |
| 6.1.0 | 14 / 0 | |
| 6.0.3 | 14 / 0 | |
| 6.0.2 | 14 / 0 | |
| 6.0.1 | 14 / 0 | |
| 6.0.0 | 14 / 0 | |
| 5.13.0 | 8 / 0 | |
| 5.12.0 | 8 / 0 | |
| 5.11.0 | 8 / 0 | |
| 5.10.0 | 8 / 0 | |
| 5.9.2 | 8 / 0 | |
| 5.9.1 | 8 / 0 | |
| 5.9.0 | 8 / 0 | |
| 5.8.3 | 8 / 0 | |
| 5.8.2 | 8 / 0 | |
| 5.8.1 | 8 / 0 | |
| 5.8.0 | 8 / 0 |
v7.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package 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.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
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.