@seayoo-web/gamer-api
agent for gamer api
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
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 4.6.5 | 0 / 10 | |
| 4.6.4 | 0 / 10 | |
| 4.6.3 | 0 / 10 | |
| 4.6.2 | 0 / 10 | |
| 4.6.1 | 0 / 10 | |
| 4.6.0 | 0 / 10 | |
| 4.5.6 | 0 / 10 | |
| 4.5.5 | 0 / 10 | |
| 4.5.4 | 0 / 10 | |
| 4.5.3 | 0 / 10 | |
| 4.5.2 | 0 / 7 | |
| 4.3.7 | 0 / 7 | |
| 4.3.6 | 0 / 7 | |
| 4.3.5 | 0 / 7 | |
| 4.3.4 | 0 / 7 | |
| 4.3.3 | 0 / 7 | |
| 4.3.2 | 0 / 7 | |
| 4.2.3 | 0 / 7 | |
| 4.2.2 | 0 / 7 | |
| 4.2.1 | 0 / 7 | |
| 4.2.0 | 0 / 7 | |
| 4.1.4 | 0 / 7 | |
| 4.1.3 | 0 / 7 | |
| 4.1.2 | 0 / 7 | |
| 4.1.1 | 0 / 7 | |
| 4.1.0 | 0 / 7 | |
| 4.0.5 | 0 / 7 | |
| 4.0.4 | 0 / 7 | |
| 4.0.3 | 0 / 7 | |
| 4.0.2 | 0 / 7 | |
| 4.0.1 | 0 / 7 | |
| 4.0.0 | 0 / 7 | |
| 3.0.4 | 0 / 7 | |
| 3.0.3 | 0 / 7 | |
| 3.0.2 | 0 / 7 | |
| 3.0.1 | 0 / 7 | |
| 3.0.0 | 0 / 7 | |
| 2.16.3 | 0 / 7 | |
| 2.16.2 | 0 / 7 | |
| 2.16.1 | 0 / 7 | |
| 2.16.0 | 0 / 7 | |
| 2.15.7 | 0 / 7 | |
| 2.15.6 | 0 / 7 | |
| 2.15.5 | 0 / 7 | |
| 2.15.4 | 0 / 7 | |
| 2.15.3 | 0 / 7 | |
| 2.15.2 | 0 / 7 | |
| 2.15.1 | 0 / 7 | |
| 2.15.0 | 0 / 7 | |
| 2.14.5 | 0 / 7 | |
| 2.14.4 | 0 / 7 |
v4.6.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zjcn5205) than the most recent previously approved version (celixld) on 2026-07-22, but zjcn5205 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (celixld) than the most recent previously approved version (zjcn5205) on 2026-07-17, but celixld is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zjcn5205) than the most recent previously approved version (zhengqiangli) on 2026-07-13, but zjcn5205 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zhengqiangli) than the most recent previously approved version (zjcn5205) on 2026-07-08, but zhengqiangli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (niboac) than the most recent previously approved version (zjcn5205) on 2026-07-08, but niboac is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.