@quenty/teamtracker
Tracks a player's current team, since the Team property is unreliable
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 NevermoreEngine monorepo; publisher has 887 approved packages and strong track record — gap likely reflects normal dev cadence. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement pattern used consistently across the NevermoreEngine monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua/Roblox bundled deps. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua/Roblox bundled deps. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org Roblox Lua package; phantom-dep heuristic unreliable for Lua/Roblox bundled deps. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 13.31.0 | 3 / 0 | |
| 13.30.2 | 3 / 0 | |
| 13.29.0 | 3 / 0 | |
| 13.28.0 | 3 / 0 | |
| 13.27.0 | 3 / 0 | |
| 13.26.0 | 3 / 0 | |
| 13.24.0 | 3 / 0 | |
| 13.23.2 | 3 / 0 | |
| 13.23.1 | 3 / 0 | |
| 13.23.0 | 3 / 0 | |
| 13.22.1 | 3 / 0 | |
| 13.22.0 | 3 / 0 | |
| 13.21.7 | 3 / 0 | |
| 13.21.6 | 3 / 0 | |
| 13.21.5 | 3 / 0 | |
| 13.21.4 | 3 / 0 | |
| 13.21.3 | 3 / 0 | |
| 13.21.2 | 3 / 0 | |
| 13.21.1 | 3 / 0 | |
| 13.21.0 | 3 / 0 | |
| 13.20.0 | 3 / 0 | |
| 13.19.0 | 3 / 0 | |
| 13.18.1 | 3 / 0 | |
| 13.18.0 | 3 / 0 |
v13.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.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.
v13.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.
v13.28.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.
v13.27.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.
v13.26.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.
v13.24.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.
v13.23.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.
v13.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.
v13.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.