@homer0/simple-config
Simple configuration management for your projects.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@homer0/root-file | AI (dependencies): Same-author monorepo sibling package; consistently co-versioned across all releases of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.0.9 | 5 / 8 | |
| 5.0.8 | 5 / 9 | |
| 5.0.7 | 5 / 9 | |
| 5.0.6 | 5 / 9 | |
| 5.0.5 | 5 / 9 | |
| 5.0.4 | 5 / 9 | |
| 5.0.3 | 5 / 9 | |
| 5.0.2 | 5 / 9 | |
| 5.0.1 | 5 / 9 | |
| 5.0.0 | 5 / 9 |
v5.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.