@walkeros/explorer
Interactive React components for walkerOS documentation and exploration
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@walkeros/web-core | AI (phantom-deps): Same-org dep; phantom-dep heuristic fires because it's not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:@rjsf/validator-ajv8 | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; CI/CD publishing is the documented pattern for this org. | ai | |
| phantom-deps | phantom-dep:@rjsf/core | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are sibling @walkeros/* packages from the same org/monorepo, not third-party additions. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo package from elbwalker org; missing gitHead reflects CI change, not supply-chain compromise. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 15 / 26 | |
| 4.1.1 | 15 / 26 | |
| 4.1.0 | 15 / 26 | |
| 4.0.2 | 14 / 26 | |
| 4.0.1 | 14 / 26 | |
| 4.0.0 | 14 / 26 | |
| 3.4.2 | 14 / 26 | |
| 3.4.1 | 14 / 26 | |
| 3.4.0 | 14 / 26 | |
| 3.3.1 | 13 / 26 | |
| 3.3.0 | 13 / 26 | |
| 3.2.0 | 13 / 26 | |
| 3.1.1 | 13 / 26 | |
| 3.1.0 | 13 / 26 | |
| 3.0.2 | 13 / 26 | |
| 3.0.1 | 13 / 26 | |
| 3.0.0 | 13 / 26 | |
| 2.1.5 | 13 / 26 | |
| 2.1.4 | 13 / 32 | |
| 2.1.3 | 13 / 32 | |
| 2.1.2 | 13 / 32 | |
| 2.1.1 | 13 / 32 | |
| 2.1.0 | 13 / 32 | |
| 2.0.1 | 13 / 32 | |
| 1.0.2 | 10 / 35 | |
| 1.0.1 | 10 / 35 | |
| 1.0.0 | 10 / 35 | |
| 0.5.0 | 8 / 34 | |
| 0.3.1 | 8 / 23 |
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
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: alexanderkirtzel.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.