@rocicorp/logger
6
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
arvaboodmancesaraz1grgbkr0xcadamstantamandarick
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI/CD publish via GitHub Actions with SLSA provenance; gitHead absence is expected when using Sigstore attestation workflow. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI publishing with SLSA provenance; official rocicorp org repo unchanged. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with team transition; package is established with 52k+ weekly downloads and no malicious indicators. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 0 / 6 | |
| 6.0.0 | 0 / 6 | |
| 5.5.0 | 0 / 6 | |
| 5.4.0 | 0 / 6 | |
| 5.3.0 | 0 / 11 | |
| 5.2.2 | 0 / 11 |
v5.3.0
2 findings
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
INFO
Publisher changed: arv → aboodman (on 2024-10-09, known maintainer)
provenance
This version was published by a different npm account (aboodman) than the most recent previously approved version (arv) on 2024-10-09, but aboodman 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.
v5.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.