@kubernetes-models/knative
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:_schemas/EventingKnativeDevV1alpha1EventPolicy.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/EventingKnativeDevV1alpha1EventTransform.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/EventingKnativeDevV1alpha1RequestReply.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/EventingKnativeDevV1beta2EventType.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/EventingKnativeDevV1beta3EventType.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/SinksKnativeDevV1alpha1IntegrationSink.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/SinksKnativeDevV1alpha1JobSink.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| source-diff | obfuscated-file:_schemas/SourcesKnativeDevV1alpha1IntegrationSource.js | AI (source-diff): Minified AJV validator output from build pipeline; no malicious code. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; consistent with CI/CD automation from legitimate maintainer. | ai | |
| phantom-deps | phantom-dep:@kubernetes-models/validate | AI (phantom-deps): Same-org dep used in generated schema files; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 3 | |
| 3.0.1 | 3 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.4.4 | 4 / 3 | |
| 2.4.3 | 4 / 3 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. 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.
v3.0.1
10 findingsThis version was published by a different npm account than previous versions on 2026-05-06. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
10 findingsThis version was published by a different npm account than previous versions on 2026-05-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.