@fiscozen/actionlist
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata gap only; trusted publisher, no behavioral change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a sibling first-party @fiscozen package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal design system component; missing metadata is typical for private org packages, not spam. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.15 | 1 / 18 | |
| 0.1.14 | 1 / 18 | |
| 0.1.13 | 1 / 18 | |
| 0.1.12 | 1 / 18 | |
| 0.1.10 | 1 / 18 | |
| 0.1.9 | 1 / 18 | |
| 0.1.8 | 1 / 18 | |
| 0.1.7 | 1 / 18 | |
| 0.1.6 | 1 / 18 | |
| 0.1.5 | 1 / 18 | |
| 0.1.4 | 1 / 18 | |
| 0.1.3 | 1 / 18 | |
| 0.1.2 | 1 / 18 | |
| 0.1.1 | 0 / 18 | |
| 0.1.0 | 0 / 18 |
v0.1.8
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: trebh.
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 2025-04-30, 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.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alen_fiscozen.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.