@elliemae/ds-page-header-v1
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
encw.dev
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): High-volume publisher with strong track record; missing gitHead is a CI environment change, not a malicious indicator for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo with 649 versions; version rollback/backport explains the gap without indicating takeover. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-legacy-page-header-v1 | AI (dependencies): Sibling package in the same @elliemae/ds-* monorepo; expected internal dependency pattern. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal design system package; no provenance is consistent across all versions in this registry. | ai |
v3.29.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.