@quenty/teleportserviceutils
Utility functions for teleport srevice
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Quenty's monorepo publishes in bulk; long gaps between releases are normal for utility sub-packages. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. Same-org dep declared correctly. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard monorepo package manager enforcement; stable pattern across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua package; JS import analysis is not applicable. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 9.31.0 | 6 / 1 | |
| 9.30.2 | 6 / 1 | |
| 9.30.0 | 6 / 1 | |
| 9.29.0 | 6 / 1 | |
| 9.23.1 | 6 / 1 | |
| 9.22.0 | 6 / 1 | |
| 9.21.6 | 6 / 1 | |
| 9.21.3 | 6 / 1 | |
| 9.21.2 | 6 / 1 | |
| 9.20.0 | 6 / 1 | |
| 9.19.0 | 6 / 1 | |
| 9.18.1 | 6 / 1 | |
| 9.18.0 | 6 / 1 |
v9.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.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.
v9.30.0
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.
v9.29.0
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.
v9.23.1
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.
v9.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.