@push.rocks/smartdata
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/lik | AI (dependencies): Same-org @push.rocks scope; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@push.rocks/smarttime | AI (dependencies): Same-org @push.rocks scope; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartdelay | AI (dependencies): Same-org @push.rocks scope; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartstring | AI (dependencies): Same-org @push.rocks scope; consistent pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher uses a self-hosted forge, not GitHub Actions. | ai | |
| phantom-deps | phantom-dep:@push.rocks/smartmongo | AI (phantom-deps): Same-org dependency; declared in package.json as a runtime dep, phantom detection is a false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 7.1.7 | 12 / 5 | |
| 7.1.6 | 12 / 5 | |
| 7.1.5 | 12 / 5 | |
| 7.1.4 | 12 / 5 | |
| 7.1.3 | 12 / 5 | |
| 7.1.2 | 12 / 5 | |
| 7.1.1 | 12 / 5 | |
| 7.1.0 | 12 / 6 | |
| 7.0.15 | 12 / 6 | |
| 7.0.14 | 12 / 6 | |
| 7.0.13 | 12 / 6 | |
| 7.0.12 | 12 / 6 | |
| 7.0.9 | 12 / 6 | |
| 7.0.8 | 12 / 6 | |
| 7.0.7 | 12 / 6 | |
| 7.0.6 | 12 / 6 | |
| 7.0.5 | 12 / 6 | |
| 7.0.4 | 12 / 6 | |
| 7.0.3 | 12 / 6 | |
| 7.0.2 | 12 / 6 | |
| 7.0.1 | 12 / 6 | |
| 7.0.0 | 12 / 6 | |
| 5.16.7 | 12 / 6 | |
| 5.16.6 | 12 / 6 |
v7.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.