@terascope/data-mate
Library of data validations/transformations
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): CIDR/IP deps align with library's validation/transformation purpose. | ai | |
| provenance | missing-githead | AI (provenance): Trusted CI publisher with long clean history; likely monorepo publish config change. | ai | |
| dependencies | unvetted-dep:ip6addr | AI (dependencies): ip6addr is a legitimate IPv6 parsing library; appropriate for this data-validation/transformation package. | ai | |
| phantom-deps | phantom-dep:big-json | AI (phantom-deps): big-json is a declared runtime dep used in config/conditional paths; phantom-dep heuristic fires as false positive. | ai | |
| phantom-deps | phantom-dep:@types/validator | AI (phantom-deps): @types/validator is a type-only dep loaded by convention; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are expected for internal library packages. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.16.0 | 20 / 6 | |
| 2.15.0 | 20 / 6 | |
| 2.14.0 | 20 / 6 | |
| 2.13.2 | 20 / 6 | |
| 2.13.1 | 20 / 6 | |
| 2.13.0 | 20 / 6 | |
| 2.12.1 | 20 / 6 | |
| 2.12.0 | 20 / 6 | |
| 2.11.1 | 20 / 6 | |
| 2.11.0 | 20 / 5 | |
| 2.10.1 | 16 / 5 | |
| 2.10.0 | 16 / 5 | |
| 2.9.1 | 16 / 5 | |
| 2.9.0 | 16 / 5 | |
| 2.8.0 | 16 / 5 | |
| 2.7.0 | 16 / 5 | |
| 2.6.3 | 16 / 5 | |
| 2.6.2 | 16 / 5 | |
| 2.6.1 | 16 / 5 | |
| 2.6.0 | 16 / 5 | |
| 2.5.2 | 16 / 5 | |
| 2.5.1 | 16 / 5 | |
| 2.5.0 | 16 / 5 | |
| 2.4.1 | 16 / 5 | |
| 2.4.0 | 16 / 5 | |
| 2.3.3 | 21 / 6 | |
| 2.3.2 | 21 / 6 | |
| 2.3.1 | 21 / 6 | |
| 2.3.0 | 21 / 6 | |
| 2.2.6 | 21 / 6 | |
| 2.2.5 | 21 / 6 | |
| 2.2.4 | 21 / 6 | |
| 2.2.3 | 19 / 6 | |
| 2.2.2 | 19 / 6 | |
| 2.2.1 | 19 / 6 | |
| 2.2.0 | 19 / 6 | |
| 2.1.0 | 19 / 6 | |
| 2.0.8 | 19 / 6 | |
| 2.0.7 | 19 / 6 | |
| 2.0.6 | 19 / 6 | |
| 2.0.5 | 19 / 6 | |
| 2.0.4 | 19 / 6 | |
| 2.0.3 | 19 / 6 | |
| 2.0.2 | 19 / 6 | |
| 2.0.1 | 19 / 6 | |
| 2.0.0 | 19 / 7 |
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.3
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-16, 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.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-11, 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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.