@terascope/ip-utils
A collection of Teraslice IP Utilities
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted CI publisher with strong track record; likely benign CI env change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): cidr-calc is a relevant, on-topic IP/CIDR dependency for this package. | ai | |
| dependencies | unvetted-dep:ip6addr | AI (dependencies): ip6addr is a well-known IPv6 parsing library; its use here is expected for an IP utilities package. | ai | |
| provenance | no-provenance | AI (provenance): Terascope org publishes without Sigstore attestation consistently; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo utility package; sparse README and no keywords are expected for internal tooling. | ai | |
| phantom-deps | phantom-dep:@terascope/types | AI (phantom-deps): Same-org transitive dep; stable false positive for this monorepo package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 2.16.0 | 2 / 1 | |
| 2.15.0 | 2 / 1 | |
| 2.14.0 | 2 / 1 | |
| 2.13.1 | 2 / 1 | |
| 2.13.0 | 2 / 1 | |
| 2.12.1 | 2 / 1 | |
| 2.12.0 | 2 / 1 | |
| 2.11.1 | 2 / 1 | |
| 2.11.0 | 2 / 0 | |
| 2.10.1 | 2 / 0 | |
| 2.10.0 | 2 / 0 | |
| 2.9.1 | 2 / 0 | |
| 2.9.0 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.0 | 2 / 0 | |
| 2.6.3 | 2 / 0 | |
| 2.6.2 | 2 / 0 | |
| 2.6.1 | 2 / 0 | |
| 2.6.0 | 2 / 0 | |
| 2.5.1 | 2 / 0 | |
| 2.5.0 | 2 / 0 | |
| 2.4.1 | 2 / 0 | |
| 2.4.0 | 2 / 0 | |
| 2.3.2 | 9 / 1 | |
| 2.3.1 | 9 / 1 | |
| 2.3.0 | 9 / 1 | |
| 2.2.4 | 9 / 1 | |
| 2.2.3 | 9 / 1 | |
| 2.2.2 | 8 / 1 | |
| 2.2.1 | 8 / 1 | |
| 2.2.0 | 8 / 1 | |
| 2.1.0 | 8 / 1 | |
| 2.0.8 | 8 / 1 | |
| 2.0.7 | 8 / 1 | |
| 2.0.6 | 8 / 1 | |
| 2.0.5 | 8 / 1 | |
| 2.0.4 | 8 / 1 | |
| 2.0.3 | 8 / 1 | |
| 2.0.2 | 8 / 1 | |
| 2.0.1 | 8 / 1 | |
| 2.0.0 | 8 / 1 |
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (terascope-ci) on 2026-03-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: terascope-ci.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.