birecord
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
kiwiyoucirnovfinalchildsupremesondisjukr
Keywords
birecordbimapbidirectional
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legit manual→CI/CD transition with SLSA attestation, same org repo. | ai | |
| provenance | missing-githead | AI (provenance): Expected when moving to CI/CD-attested publish. | ai |
v0.1.2
3 findings
HIGH
Missing gitHead — previous versions had it
provenance
This 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.
HIGH
Publisher changed: disjukr → GitHub Actions (on 2026-07-09)
provenance
This version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.