@quenty/racketingropeconstraint
Tries to racket a rope constraint back down to a reasonable length
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package-manager enforcement pattern; stable across all @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/tie | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/binder | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/overriddenproperty | AI (phantom-deps): Same-org monorepo dependency; indirect imports are expected in this package structure. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 12.40.2 | 8 / 0 | |
| 12.32.0 | 8 / 0 | |
| 12.31.1 | 8 / 0 | |
| 12.31.0 | 8 / 0 | |
| 12.30.0 | 8 / 0 | |
| 12.29.1 | 8 / 0 | |
| 12.29.0 | 8 / 0 | |
| 12.28.7 | 8 / 0 | |
| 12.28.6 | 7 / 0 | |
| 12.28.5 | 7 / 0 | |
| 12.28.4 | 7 / 0 | |
| 12.28.3 | 7 / 0 | |
| 12.28.2 | 7 / 0 | |
| 12.28.1 | 7 / 0 | |
| 12.28.0 | 7 / 0 | |
| 12.27.1 | 7 / 0 | |
| 12.27.0 | 7 / 0 | |
| 12.26.0 | 7 / 0 | |
| 12.25.0 | 7 / 0 | |
| 12.24.0 | 7 / 0 | |
| 12.23.0 | 7 / 0 | |
| 12.22.1 | 7 / 0 | |
| 12.22.0 | 7 / 0 | |
| 12.21.0 | 7 / 0 |
v12.40.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.
v12.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.