@quenty/transitionmodel
Helps with Gui visiblity showing and hiding
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Lua test dep, not scannable by JS import analysis; consistent with monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same-org Lua test dep, not imported via JS require. | ai | |
| dependencies | unvetted-dep:@quentystudios/jest-lua | AI (dependencies): Known Lua test framework fork, benign test tooling. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep publishing pattern for this trusted publisher. | ai | |
| dependencies | unvetted-dep:@quenty/rx | AI (dependencies): Same @quenty org scope; consistent pattern across all NevermoreEngine packages. | ai | |
| provenance | no-provenance | AI (provenance): Quenty monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@quenty/spring | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/basicpane | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern across all quenty packages. | ai | |
| phantom-deps | phantom-dep:@quenty/timedtween | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/blend | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Roblox/Lua monorepo; JS import analysis doesn't apply to Lua source files. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 7.46.0 | 15 / 0 | |
| 7.45.0 | 13 / 0 | |
| 7.44.0 | 13 / 0 | |
| 7.43.0 | 13 / 0 | |
| 7.42.1 | 13 / 0 | |
| 7.42.0 | 13 / 0 | |
| 7.41.0 | 13 / 0 | |
| 7.40.0 | 13 / 0 | |
| 7.39.0 | 13 / 0 | |
| 7.38.1 | 13 / 0 | |
| 7.38.0 | 13 / 0 | |
| 7.37.0 | 13 / 0 | |
| 7.36.2 | 13 / 0 | |
| 7.36.1 | 13 / 0 | |
| 7.36.0 | 13 / 0 | |
| 7.35.0 | 13 / 0 | |
| 7.34.0 | 13 / 0 | |
| 7.33.0 | 13 / 0 | |
| 7.32.0 | 13 / 0 | |
| 7.31.0 | 13 / 0 | |
| 7.30.2 | 13 / 0 | |
| 7.30.1 | 13 / 0 | |
| 7.30.0 | 13 / 0 | |
| 7.29.0 | 13 / 0 | |
| 7.28.0 | 13 / 0 | |
| 7.27.1 | 13 / 0 | |
| 7.27.0 | 13 / 0 | |
| 7.26.1 | 13 / 0 | |
| 7.26.0 | 13 / 0 | |
| 7.25.0 | 13 / 0 | |
| 7.24.1 | 13 / 0 | |
| 7.24.0 | 13 / 0 | |
| 7.23.7 | 13 / 0 | |
| 7.23.6 | 13 / 0 | |
| 7.23.5 | 13 / 0 | |
| 7.23.4 | 13 / 0 | |
| 7.23.3 | 13 / 0 | |
| 7.23.2 | 13 / 0 | |
| 7.23.1 | 13 / 0 | |
| 7.23.0 | 13 / 0 | |
| 7.22.0 | 13 / 0 | |
| 7.21.0 | 13 / 0 | |
| 7.20.1 | 13 / 0 | |
| 7.20.0 | 13 / 0 | |
| 7.19.3 | 13 / 0 | |
| 7.19.2 | 13 / 0 | |
| 7.19.0 | 13 / 0 | |
| 7.18.2 | 13 / 0 | |
| 7.18.1 | 13 / 0 | |
| 7.18.0 | 13 / 0 | |
| 7.17.0 | 13 / 0 |
v7.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.