@times-components/jest-serializer
serializer
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/jest-configurator | AI (dependencies): Sibling package in same monorepo/org, not an external unvetted dep. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-managed monorepo maintainer rotation, no suspicious new maintainer added. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; consistent with package history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): css/hyphenate-style-name are established, function-appropriate deps. | ai | |
| phantom-deps | phantom-dep:@times-components/utils | AI (phantom-deps): Same-org monorepo dependency; declared in package.json, stable false positive for this package. | ai |
Versions (showing 100 of 103)
| Version | Deps | Published |
|---|---|---|
| 3.18.21 | 6 / 12 | |
| 3.18.20 | 6 / 12 | |
| 3.18.19 | 6 / 12 | |
| 3.18.18 | 6 / 12 | |
| 3.18.17 | 6 / 12 | |
| 3.18.16 | 6 / 12 | |
| 3.18.15 | 6 / 12 | |
| 3.18.14 | 6 / 12 | |
| 3.18.13 | 6 / 12 | |
| 3.18.12 | 6 / 12 | |
| 3.18.11 | 6 / 12 | |
| 3.18.10 | 6 / 12 | |
| 3.18.9 | 6 / 12 | |
| 3.18.8 | 6 / 12 | |
| 3.18.7 | 6 / 12 | |
| 3.18.6 | 6 / 12 | |
| 3.18.5 | 6 / 12 | |
| 3.18.4 | 6 / 12 | |
| 3.18.3 | 6 / 12 | |
| 3.18.2 | 6 / 12 | |
| 3.18.1 | 6 / 12 | |
| 3.18.0 | 6 / 12 | |
| 3.17.0 | 6 / 12 | |
| 3.16.1 | 6 / 12 | |
| 3.16.0 | 6 / 12 | |
| 3.15.0 | 6 / 12 | |
| 3.14.0 | 6 / 12 | |
| 3.13.28 | 6 / 12 | |
| 3.13.27 | 6 / 12 | |
| 3.13.26 | 6 / 12 | |
| 3.13.25 | 6 / 12 | |
| 3.13.24 | 6 / 12 | |
| 3.13.23 | 6 / 12 | |
| 3.13.22 | 6 / 12 | |
| 3.13.21 | 6 / 12 | |
| 3.13.20 | 6 / 12 | |
| 3.13.19 | 6 / 12 | |
| 3.13.18 | 6 / 12 | |
| 3.13.17 | 6 / 12 | |
| 3.13.16 | 6 / 12 | |
| 3.13.15 | 6 / 12 | |
| 3.13.14 | 6 / 12 | |
| 3.13.13 | 6 / 12 | |
| 3.13.12 | 6 / 12 | |
| 3.13.11 | 6 / 12 | |
| 3.13.10 | 6 / 12 | |
| 3.13.9 | 6 / 12 | |
| 3.13.8 | 6 / 12 | |
| 3.13.7 | 6 / 12 | |
| 3.13.6 | 6 / 12 | |
| 3.13.5 | 6 / 12 | |
| 3.13.4 | 6 / 12 | |
| 3.13.3 | 6 / 12 | |
| 3.13.2 | 6 / 12 | |
| 3.13.1 | 6 / 12 | |
| 3.13.0 | 6 / 12 | |
| 3.12.4 | 6 / 12 | |
| 3.12.3 | 6 / 12 | |
| 3.12.2 | 6 / 12 | |
| 3.12.1 | 6 / 12 | |
| 3.12.0 | 6 / 12 | |
| 3.11.0 | 6 / 12 | |
| 3.10.1 | 6 / 12 | |
| 3.9.1 | 6 / 12 | |
| 3.9.0 | 6 / 12 | |
| 3.8.3 | 6 / 12 | |
| 3.8.1 | 6 / 12 | |
| 3.8.0 | 6 / 12 | |
| 3.7.2 | 6 / 12 | |
| 3.7.1 | 6 / 12 | |
| 3.7.0 | 6 / 12 | |
| 3.6.0 | 6 / 12 | |
| 3.5.5 | 6 / 12 | |
| 3.5.4 | 6 / 12 | |
| 3.5.3 | 6 / 12 | |
| 3.5.2 | 6 / 12 | |
| 3.5.1 | 6 / 12 | |
| 3.5.0 | 6 / 12 | |
| 3.4.2 | 6 / 12 | |
| 3.4.1 | 6 / 12 | |
| 3.4.0 | 6 / 12 | |
| 3.2.28 | 6 / 14 | |
| 3.2.22 | 6 / 14 | |
| 3.2.10 | 6 / 14 | |
| 3.2.2 | 5 / 12 | |
| 3.2.1 | 5 / 12 | |
| 3.2.0 | 5 / 12 | |
| 3.1.13 | 5 / 12 | |
| 3.1.12 | 5 / 12 | |
| 3.1.11 | 5 / 12 | |
| 3.1.10 | 5 / 12 | |
| 3.1.9 | 5 / 12 | |
| 3.1.8 | 5 / 12 | |
| 3.1.7 | 5 / 12 | |
| 3.1.6 | 5 / 12 | |
| 3.1.5 | 3 / 12 | |
| 3.1.4 | 3 / 12 | |
| 3.1.3 | 3 / 12 | |
| 3.1.2 | 3 / 12 | |
| 3.1.1 | 3 / 11 |
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
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: craigbilner.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (craigbilner) than the most recent previously approved version (news-tools) on 2018-11-06, but craigbilner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.