@quenty/receiptprocessing
Centralize receipt processing within games since this is a constrained resource.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 550 approved packages and zero rejections; dormancy likely reflects normal release cadence for this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; imports not detected by standard JS static analysis. Same-org dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package manager enforcement; stable across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@quenty/enumutils | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Roblox/Lua package; same-org dep, stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.33.0 | 8 / 0 | |
| 7.32.2 | 8 / 0 | |
| 7.29.0 | 8 / 0 | |
| 7.28.0 | 8 / 0 | |
| 7.27.0 | 8 / 0 | |
| 7.25.0 | 8 / 0 | |
| 7.24.1 | 8 / 0 | |
| 7.23.3 | 8 / 0 | |
| 7.23.2 | 8 / 0 | |
| 7.23.0 | 8 / 0 | |
| 7.22.0 | 8 / 0 | |
| 7.21.0 | 8 / 0 | |
| 7.20.1 | 8 / 0 | |
| 7.20.0 | 8 / 0 | |
| 7.19.0 | 8 / 0 |
v7.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.2
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.