@verii/endpoints-credential-types-registrar
Credential Types Registrar
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:@fastify/helmet | AI (dependencies): @fastify/helmet is a well-known, widely-used Fastify security plugin; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@fastify/autoload | AI (dependencies): @fastify/autoload is a well-known official Fastify plugin; unvetted status is a registry gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@fastify/sensible | AI (dependencies): @fastify/sensible is a well-known official Fastify plugin; unvetted status is a registry gap, not a real risk. | ai | |
| phantom-deps | phantom-dep:@fastify/sensible | AI (phantom-deps): Fastify plugins loaded via autoload config pattern; phantom-dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): Fastify is loaded via @fastify/autoload from config; not directly imported is expected for this microservice pattern. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger-ui | AI (phantom-deps): Fastify plugins loaded via autoload config pattern; phantom-dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/helmet | AI (phantom-deps): Fastify plugins loaded via autoload config pattern; phantom-dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger | AI (phantom-deps): Fastify plugins loaded via autoload config pattern; phantom-dep finding is a stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 21 / 22 | |
| 1.1.2 | 21 / 22 | |
| 1.1.1 | 21 / 22 | |
| 1.1.0 | 21 / 22 | |
| 1.0.9 | 21 / 21 | |
| 1.0.8 | 21 / 21 | |
| 1.0.7 | 21 / 21 | |
| 1.0.6 | 21 / 21 | |
| 1.0.5 | 21 / 21 | |
| 1.0.4 | 21 / 21 | |
| 1.0.3 | 21 / 21 | |
| 1.0.2 | 21 / 21 | |
| 1.0.1 | 21 / 21 | |
| 1.0.0 | 21 / 21 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.