@fiscozen/navbar
Design System Navbar Component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fiscozen/button | AI (phantom-deps): Same-org dep likely re-exported; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/composables | AI (phantom-deps): Same-org dep likely re-exported; stable FP for this package. | ai | |
| provenance | no-provenance | AI (provenance): Common for internal/org-scoped packages; not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal design-system component; sparse metadata is expected for org-scoped packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 3 / 18 | |
| 0.3.2 | 3 / 18 | |
| 0.3.1 | 3 / 18 | |
| 0.3.0 | 3 / 18 | |
| 0.2.1 | 3 / 18 | |
| 0.1.11 | 3 / 18 | |
| 0.1.5 | 2 / 18 | |
| 0.1.4 | 2 / 18 | |
| 0.1.3 | 0 / 18 | |
| 0.1.2 | 0 / 18 | |
| 0.1.1 | 0 / 18 | |
| 0.1.0 | 0 / 18 |
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (trebh) than the most recent previously approved version (alen_fiscozen) on 2024-11-19, but trebh 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.
v0.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (trebh) on 2024-11-19, but alen_fiscozen 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.
v0.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (trebh) on 2024-10-31, but alen_fiscozen 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.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.