@quenty/adorneevalue
Adorneevalue - Helper class to transform a an adornee into relative positions/information.
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 | rapid-publish | AI (publish-pattern): Monorepo lockstep publishing across @quenty packages, benign pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; deps declared for Lua tooling, not JS imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| phantom-deps | phantom-dep:@quenty/blend | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement pattern used across the NevermoreEngine monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| phantom-deps | phantom-dep:@quenty/adorneeutils | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same as above — Lua monorepo pattern, not a JS import issue. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 10.43.0 | 8 / 0 | |
| 10.41.1 | 8 / 0 | |
| 10.40.0 | 8 / 0 | |
| 10.38.0 | 8 / 0 | |
| 10.36.0 | 8 / 0 | |
| 10.34.0 | 8 / 0 | |
| 10.25.0 | 8 / 0 | |
| 10.24.1 | 8 / 0 | |
| 10.24.0 | 8 / 0 | |
| 10.23.7 | 8 / 0 | |
| 10.23.6 | 8 / 0 | |
| 10.23.5 | 7 / 0 | |
| 10.23.4 | 7 / 0 | |
| 10.23.3 | 7 / 0 | |
| 10.23.2 | 7 / 0 | |
| 10.23.1 | 7 / 0 | |
| 10.23.0 | 7 / 0 | |
| 10.22.0 | 7 / 0 | |
| 10.21.0 | 7 / 0 | |
| 10.20.1 | 7 / 0 | |
| 10.20.0 | 7 / 0 | |
| 10.19.0 | 6 / 0 | |
| 10.18.3 | 6 / 0 | |
| 10.18.2 | 6 / 0 | |
| 10.18.1 | 6 / 0 | |
| 10.18.0 | 6 / 0 | |
| 10.17.2 | 6 / 0 | |
| 10.17.1 | 6 / 0 | |
| 10.17.0 | 6 / 0 | |
| 10.16.0 | 6 / 0 | |
| 10.15.0 | 6 / 0 | |
| 10.14.0 | 6 / 0 | |
| 10.13.0 | 6 / 0 | |
| 10.12.0 | 6 / 0 | |
| 10.11.1 | 6 / 0 | |
| 10.11.0 | 6 / 0 | |
| 10.10.0 | 6 / 0 | |
| 10.9.2 | 6 / 0 | |
| 10.9.1 | 6 / 0 | |
| 10.9.0 | 6 / 0 | |
| 10.8.1 | 6 / 0 | |
| 10.8.0 | 6 / 0 | |
| 10.7.0 | 6 / 0 | |
| 10.6.0 | 6 / 0 | |
| 10.5.2 | 6 / 0 | |
| 10.5.1 | 6 / 0 | |
| 10.5.0 | 6 / 0 | |
| 10.4.0 | 6 / 0 | |
| 10.3.0 | 6 / 0 |
v10.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.