@convex-dev/sharded-counter
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): New maintainers (dowski-convex, reece-convex, sethconvex) all follow the org naming pattern; consistent with internal team expansion at Convex. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of ballingt alongside addition of org-named maintainers indicates a planned team transition, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 223-day gap explained by organizational transition; package is actively maintained by the Convex org. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 0 / 29 | |
| 0.2.0 | 0 / 29 | |
| 0.1.8 | 0 / 10 | |
| 0.1.7 | 0 / 10 | |
| 0.1.6 | 0 / 10 | |
| 0.1.5 | 0 / 10 | |
| 0.1.4 | 0 / 10 | |
| 0.1.3 | 0 / 10 | |
| 0.1.2 | 0 / 10 | |
| 0.1.1 | 0 / 10 |
v0.1.7
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 (ballingt) than the most recent previously approved version (ianatconvex) on 2025-02-05, but ballingt 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.
v0.1.6
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 (ballingt) than the most recent previously approved version (ianatconvex) on 2025-01-14, but ballingt 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.
v0.1.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 (ianatconvex) than the most recent previously approved version (sujayakar) on 2025-01-02, but ianatconvex 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.
v0.1.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 (ldanilek) than the most recent previously approved version (sujayakar) on 2024-10-22, but ldanilek 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.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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 (sujayakar) than the most recent previously approved version (ldanilek) on 2024-10-18, but sujayakar 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.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.