@push.rocks/smartlog
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@push.rocks/smartfile | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smarthash | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smarttime | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has no provenance attestation history but is otherwise clean. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 9 / 5 | |
| 3.2.1 | 10 / 5 | |
| 3.2.0 | 10 / 5 | |
| 3.1.11 | 10 / 5 | |
| 3.1.10 | 10 / 5 | |
| 3.1.9 | 10 / 5 | |
| 3.1.8 | 10 / 5 | |
| 3.1.7 | 10 / 5 | |
| 3.1.3 | 10 / 5 | |
| 3.1.2 | 10 / 5 | |
| 3.1.1 | 10 / 6 | |
| 3.0.9 | 11 / 6 | |
| 3.0.8 | 11 / 6 |
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.