@verii/endpoints-event-processing
Event processing
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation present, indicating intentional CI/CD migration for this org's monorepo. Consistent repo URL and coordinated version bump confirm legitimacy. | ai | |
| provenance | no-provenance | AI (provenance): LFDT-Verii is an established Linux Foundation org; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): Fastify apps using @fastify/autoload load plugins from filesystem; direct imports are not required. Standard Fastify application pattern. | ai | |
| phantom-deps | phantom-dep:@fastify/helmet | AI (phantom-deps): Loaded via @fastify/autoload plugin discovery pattern, not direct import. Expected for Fastify applications. | ai | |
| phantom-deps | phantom-dep:@fastify/sensible | AI (phantom-deps): Loaded via @fastify/autoload plugin discovery pattern, not direct import. Expected for Fastify applications. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is a configurable default for a blockchain RPC node endpoint (env var RPC_NODE_URL with fallback). Standard pattern for blockchain infrastructure packages. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger-ui | AI (phantom-deps): Loaded via @fastify/autoload plugin discovery pattern, not direct import. Expected for Fastify applications. | ai | |
| phantom-deps | phantom-dep:@verii/endpoints-organizations-registrar | AI (phantom-deps): Same-org monorepo sibling, likely loaded dynamically or via autoload. Not a malicious phantom dep. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger | AI (phantom-deps): Loaded via @fastify/autoload plugin discovery pattern, not direct import. Expected for Fastify applications. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of blockchain event data is core functionality for an Ethereum event processing package. Buffer.from(hex).toString() is standard and not obfuscation. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 26 / 18 | |
| 1.1.2 | 26 / 18 | |
| 1.1.1 | 26 / 18 | |
| 1.1.0 | 26 / 18 | |
| 1.0.9 | 26 / 17 | |
| 1.0.8 | 26 / 17 | |
| 1.0.7 | 26 / 17 | |
| 1.0.6 | 26 / 17 | |
| 1.0.5 | 26 / 17 | |
| 1.0.4 | 26 / 17 | |
| 1.0.3 | 26 / 17 | |
| 1.0.2 | 26 / 17 | |
| 1.0.1 | 26 / 17 | |
| 1.0.0 | 26 / 17 |
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.