@quenty/counter
Helps count a total value
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
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): Quenty monorepo package with 208 prior versions and clean publisher history; dormancy consistent with batch release cadence. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; deps declared for tooling, not JS imports. Same-org scope. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org Lua package; no JS imports expected. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Lua package; no JS imports expected. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard only-allow pnpm enforcer; stable pattern across all @quenty/* monorepo packages. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same-org Lua package; no JS imports expected. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org Lua package; no JS imports expected. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org Lua package; no JS imports expected. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 7.31.0 | 6 / 0 | |
| 7.30.2 | 6 / 0 | |
| 7.29.0 | 6 / 0 | |
| 7.21.3 | 6 / 0 | |
| 7.20.0 | 5 / 0 | |
| 7.19.0 | 5 / 0 | |
| 7.18.1 | 5 / 0 | |
| 7.17.3 | 5 / 0 | |
| 7.17.2 | 5 / 0 | |
| 7.17.1 | 5 / 0 | |
| 7.17.0 | 5 / 0 | |
| 7.16.2 | 5 / 0 | |
| 7.16.1 | 5 / 0 | |
| 7.16.0 | 5 / 0 | |
| 7.15.0 | 5 / 0 | |
| 7.14.0 | 5 / 0 | |
| 7.13.0 | 5 / 0 | |
| 7.12.0 | 5 / 0 | |
| 7.11.1 | 5 / 0 | |
| 7.11.0 | 5 / 0 | |
| 7.10.0 | 5 / 0 | |
| 7.9.2 | 5 / 0 | |
| 7.9.1 | 5 / 0 | |
| 7.9.0 | 5 / 0 | |
| 7.8.1 | 5 / 0 | |
| 7.8.0 | 5 / 0 | |
| 7.7.0 | 5 / 0 | |
| 7.6.0 | 5 / 0 | |
| 7.5.0 | 5 / 0 | |
| 7.4.0 | 5 / 0 | |
| 7.3.0 | 5 / 0 |
v7.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
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.0
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.