@verii/fastify-plugins
Plugin for handling errors
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 | slsa-provenance | AI (provenance): Package is consistently published via CI/CD with Sigstore SLSA attestation; this is a stable, positive signal for the @verii org packages. | ai | |
| phantom-deps | phantom-dep:@verii/crypto | AI (phantom-deps): Same-org sibling package declared as dependency; phantom detection is a false positive in monorepo context where transitive resolution is intended. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 10 / 14 | |
| 1.1.2 | 10 / 14 | |
| 1.1.1 | 10 / 14 | |
| 1.1.0 | 10 / 14 | |
| 1.0.9 | 10 / 14 | |
| 1.0.8 | 10 / 14 | |
| 1.0.7 | 10 / 14 | |
| 1.0.6 | 10 / 14 | |
| 1.0.5 | 10 / 14 | |
| 1.0.4 | 10 / 14 | |
| 1.0.3 | 10 / 14 | |
| 1.0.2 | 10 / 14 | |
| 1.0.1 | 10 / 14 | |
| 1.0.0 | 10 / 14 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.