@push.rocks/smartstate
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@push.rocks/lik | AI (phantom-deps): Same-org dependency declared in package.json; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; stable false positive for this package family. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in bundled dist; consistent with template/parser internals in this state management library. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in bundled dist alongside JSON/string processing code; no evidence of payload hiding. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 5 / 5 | |
| 2.3.0 | 5 / 6 | |
| 2.2.1 | 5 / 6 | |
| 2.2.0 | 5 / 6 | |
| 2.1.1 | 5 / 6 | |
| 2.1.0 | 5 / 6 | |
| 2.0.31 | 6 / 6 | |
| 2.0.30 | 6 / 6 | |
| 2.0.27 | 6 / 6 | |
| 2.0.26 | 6 / 6 | |
| 2.0.25 | 6 / 6 | |
| 2.0.23 | 6 / 6 | |
| 2.0.22 | 6 / 6 | |
| 2.0.21 | 6 / 6 | |
| 2.0.20 | 6 / 6 |
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.