@times-components/jest-serializer
serializer
3
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
marcincubernewsuknews-tools
Keywords
reactjest-serializercomponent
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 |
v3.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.