@abp/datatables.net LGPL-3.0 12 versions

@abp/datatables.net

npm Repository Homepage

ABP Framework is a complete open-source infrastructure to create modern web applications by following the best practices and conventions of software development. This package is a part of the [ABP Framework](https://abp.io) and contains client-side files.

12

Versions

LGPL-3.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

volohikalkan

Keywords

aspnetcoreboilerplateframeworkwebbest-practicesangularmauiblazormvccsharpwebapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@abp/jquery	AI (phantom-deps): Thin wrapper package; deps declared for bundling, not direct import. Stable pattern for @abp/* packages.	ai	2026/04/30
phantom-deps	phantom-dep:datatables.net	AI (phantom-deps): Same thin-wrapper pattern; datatables.net is a peer/bundled dep, not directly imported in code.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Legitimate ABP Framework wrapper package; tiny payload and link-heavy README are expected for this package type.	ai	2026/04/30

Versions (showing 12 of 12)

Version	Deps	Published
10.4.1	2 / 0	2026-06-01
10.4.0	2 / 0	2026-05-14
10.3.0	2 / 0	2026-04-15
10.2.1	2 / 0	2026-04-14
10.2.0	2 / 0	2026-03-31
10.1.1	2 / 0	2026-03-03
10.1.0	2 / 0	2026-02-17
10.0.3	2 / 0	2026-02-03
10.0.2	2 / 0	2026-01-05
10.0.1	2 / 0	2025-12-03
10.0.0	2 / 0	2025-11-18
9.3.7	2 / 0	2025-12-08

v10.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.