@b3dotfun/leaderboards
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale change (455d), stable since, likely legitimate handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with stale publisher change, not a fresh takeover signal. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change, not consistent with account compromise. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 2 / 5 | |
| 2.3.2 | 2 / 5 | |
| 2.3.1 | 2 / 5 | |
| 2.3.0 | 2 / 5 | |
| 2.2.4 | 2 / 5 | |
| 2.2.3 | 2 / 5 | |
| 2.2.2 | 2 / 5 | |
| 2.2.1 | 2 / 5 | |
| 2.1.7 | 2 / 5 | |
| 2.1.6 | 2 / 5 | |
| 2.1.5 | 2 / 5 | |
| 2.1.4 | 2 / 5 | |
| 2.1.3 | 2 / 5 | |
| 2.1.2 | 2 / 5 | |
| 2.1.1 | 2 / 5 | |
| 2.1.0 | 2 / 5 | |
| 2.0.1 | 2 / 5 | |
| 2.0.0 | 2 / 5 |
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-28. It has since remained available on npm for 446 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-28. It has since remained available on npm for 446 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-25. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 450 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 451 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-24. It has since remained available on npm for 451 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account (trung.npclabs) than the most recent previously approved version (anqt-dev) on 2025-04-19. It has since remained available on npm for 455 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.