@player-tools/dsl
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build tooling dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:jsonc-parser | AI (phantom-deps): Config/build tooling dependency; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @player-tools/dsl; levenshtein match to 'qs' is a false positive with no plausible squatting intent. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Build/config tooling dependency; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:globby | AI (phantom-deps): Config/build tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mkdirp | AI (phantom-deps): Config/build tooling dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Config/build tooling dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Config/build tooling dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/mkdirp | AI (phantom-deps): Type definitions for build tooling; stable false positive. | ai | |
| phantom-deps | phantom-dep:command-line-application | AI (phantom-deps): Config/build tooling dependency; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 16 / 0 | |
| 0.11.0 | 16 / 0 | |
| 0.10.2 | 16 / 0 | |
| 0.10.1 | 16 / 0 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.