@kne/info-page
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kne/is-empty | AI (dependencies): Same @kne org scope as this package; consistent with publisher's ecosystem pattern. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.2.13 | 6 / 9 | |
| 0.2.12 | 5 / 9 | |
| 0.2.11 | 5 / 9 | |
| 0.2.10 | 4 / 9 | |
| 0.2.9 | 4 / 9 | |
| 0.2.8 | 4 / 9 | |
| 0.2.7 | 4 / 9 | |
| 0.2.6 | 4 / 9 | |
| 0.2.5 | 4 / 9 | |
| 0.2.4 | 4 / 9 | |
| 0.2.3 | 4 / 9 | |
| 0.2.2 | 4 / 9 | |
| 0.2.1 | 4 / 9 | |
| 0.2.0 | 4 / 9 | |
| 0.1.29 | 4 / 9 | |
| 0.1.28 | 4 / 9 | |
| 0.1.27 | 4 / 9 | |
| 0.1.26 | 4 / 9 | |
| 0.1.25 | 4 / 9 | |
| 0.1.24 | 4 / 9 | |
| 0.1.23 | 4 / 9 | |
| 0.1.22 | 4 / 9 | |
| 0.1.21 | 4 / 9 | |
| 0.1.20 | 4 / 9 | |
| 0.1.19 | 4 / 9 | |
| 0.1.18 | 4 / 9 | |
| 0.1.17 | 4 / 9 | |
| 0.1.16 | 4 / 9 | |
| 0.1.15 | 4 / 9 | |
| 0.1.14 | 4 / 9 | |
| 0.1.13 | 4 / 9 | |
| 0.1.12 | 4 / 9 | |
| 0.1.11 | 4 / 9 | |
| 0.1.10 | 4 / 8 | |
| 0.1.9 | 4 / 8 | |
| 0.1.8 | 4 / 8 | |
| 0.1.7 | 4 / 8 | |
| 0.1.6 | 2 / 9 | |
| 0.1.5 | 2 / 9 | |
| 0.1.4 | 2 / 9 | |
| 0.1.3 | 2 / 9 | |
| 0.1.2 | 2 / 9 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v0.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage 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.