@quenty/remotefunctionutils
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): Part of large Roblox/NevermoreEngine monorepo; batch releases after gaps are normal for this publisher. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement pattern used across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Roblox/Lua packages with indirect imports. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Roblox/Lua packages with indirect imports. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 10.18.1 | 2 / 0 | |
| 10.18.0 | 2 / 0 | |
| 10.17.0 | 2 / 0 | |
| 10.13.0 | 2 / 0 | |
| 10.12.4 | 2 / 0 | |
| 10.12.3 | 2 / 0 | |
| 10.12.2 | 2 / 0 | |
| 10.12.1 | 2 / 0 | |
| 10.12.0 | 2 / 0 | |
| 10.11.0 | 2 / 0 | |
| 10.10.4 | 2 / 0 | |
| 10.10.3 | 2 / 0 | |
| 10.10.2 | 2 / 0 | |
| 10.10.1 | 2 / 0 | |
| 10.10.0 | 2 / 0 | |
| 10.9.0 | 2 / 0 | |
| 10.8.0 | 2 / 0 | |
| 10.7.1 | 2 / 0 | |
| 10.7.0 | 2 / 0 | |
| 10.6.0 | 2 / 0 | |
| 10.5.0 | 2 / 0 | |
| 10.4.0 | 2 / 0 | |
| 10.3.0 | 2 / 0 | |
| 10.2.0 | 2 / 0 | |
| 10.1.0 | 2 / 0 | |
| 10.0.0 | 2 / 0 |
v10.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.1
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.0
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.1
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.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.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.